What are your least/most favorite programming languages?

[XmisterIS]

For the techies of the forum, put the programming languages that you know well in order of preference.

For me, in order of most favorite to least favorite it's:

1) PHP - not strictly a programming language, I know (it's a scripting language), but I love it! It is so easy to do things very quickly, with not a lot of code and it's very readable.

2) Java - Very strongly OO, dead easy to read, very quick to develop too.

3) Python. I just think it's neat!

4) C. Lovely language for writing numerical algorithms.

5) C++. The basic OO stuff works very nicely, but operator overloading and template classes are the road to hell ...

6) Fortran 77. This language is the most restrictive, irritating, clunky, old-fashioned shitty pile of crap known to mankind!

7) Lisp. Lost-In-Silly-Parentheses ... please can I shoot myself??!!!

8) Perl. Ugh! This is the only language I know that can turn a perfectly simple expression into a whole lot of unreadable squiggles ...

 

[Carwash]

I think my list is broadly the same as your list, but in reverse.

Edit: Would have written more, but this thread topic strikes me as being slightly troll-y. It's possible that you're just genuinely interested to know what languages other people like/dislike and why, and if that's the case then all power to you. But whether that's your intention or not, the inevitable conclusion of this thread can only be people angrily attacking other people's language choices and indignantly defending their own, before someone innocently asks which is the best editor, vi or emacs. It's sad, and it'd be great to have a civilised discussion about other people's language preferences and the reasons behind them, but there it is. Do please prove me wrong - stay polite and detached, and I'll happily join in the debate with gusto.

 

[Mark_Robson]

Did I tell you about the days when I created my own programs in BBC basic?

 

[Garz]

Edit: Would have written more, but this thread topic strikes me as being slightly troll-y.

 

[2Loose]

Good --------------------------------------------> Bad

Java ........... C++ ............. C .......... VB ........... Perl






I have my reasons.

 

[XmisterIS]

Good --------------------------------------------> Bad

Java ........... C++ ............. C .......... VB ........... Perl






I have my reasons.

I am so pleased that VB is becoming a thing of the past ... it used to make me want to smash the computer! Christ, it was crap!!

Did I tell you about the days when I created my own programs in BBC basic?

Lol! I remember writing machine code for the ZX Spectrum 128K. Debugging that is enough to make a grown man weep ...

 

[TrevorM]

Best: COBOL - because it's still the best language for the job (very high volume business processes) and it runs on a real (mainframe) computer
.
.
everything else
.
.
Worst: COBOL - because it's COBOL

Then again I'm biased as I'm writing COBOL on my other computer as we speak....

 

[tyred]

I used to enjoy programming Intel 8051 chips in Assembly language. Does that make me the only one!

 

[2Loose]

I used to enjoy programming Intel 8051 chips in Assembly language. Does that make me the only one!

Yup, Intel assembly sucked hard, Motorola was where the pleasure lay.

 

[Tim Bennet.]

I found the worst was programming with Fortran using manually punched cards.
Took me about a year to get the data in, eliminate all the errors and finally have some answers for my dissertation.

Such a bad experience I have never programmed anything since.
Not even the video recorder.

 

[tyred]

Yup, Intel assembly sucked hard, Motorola was where the pleasure lay.

Funnily enough, I always struggled to get to grips with the Motorola but had no trouble with Intel.

 

[Dan B]

Horses for courses, innit? Personally I go for Ruby and Lisp and (to a lesser extent these days) Perl, but I enjoy writing C (not C++. Note to recruiters: there is no such thing as "C/C++". C and C++ are two different languages) when it's appropriate, and have even found excuses to get stuck into assembler (x86, x86-64, alpha, ppc) at times. I spent a fair chunk of time about ten years ago working on SBCL, an open-source Lisp compiler, which was a lot of fun. Ruby is approximately 85% of lisp but without the syntax (which is a shame, as macro support would pretty much enable the other 15%) and with a much larger active development community around it. I'm hoping for good things from Rubinius which should make the barrier to creating new and interesting Ruby-based languages much lower

Java was not quite as shockingly awful when I revisited last year (Android programming) as I remembered it being from when I first tried to use it (back in the 1.1 days with applets and AWT), but it's never going to be a language that changes the way someone thinks. Javascript could be a very nice language but the culture around it (cut & paste coding and script kiddies) makes it very hard to use effectively when Google can't distinguish good resources from chaff. PHP is a subject on which I will remain resolutely silent, on the principle of "if you can't say anything nice, don't say anything"

Emacs, ftr. My vi experience is sufficient to the task of editing config files as root: I know it's powerful and flexible and all that jazz, but I've been using emacs for 20-odd years now and can't see the point in learning another editor if it's not going to do anything I can't do already. I'd rather spend the time on something new and different.

http://lukewelling.c...of-programming/

 

[ian turner]

Where are the cakes ?!!!!!!!!



It doesn't matter what language you're programming in if your employer is trying to stretch the hardware to new limits it's not designed for (retail scales with 8051s using spare I/O to page select extra programming memory, the more pages the more of a page was used by common code , or military data loggers using the motorola equivalent with 256 bytes of ram, messages longer than that and flash as the storage medium )

 

[Carwash]

Ruby is approximately 85% of lisp but without the syntax

Greenspun's Tenth Rule strikes again.

 

[2Loose]

Funnily enough, I always struggled to get to grips with the Motorola but had no trouble with Intel.

Couldn't cope with more than 8 registers?