The 10 most dreaded programming languages, according to a survey of 65,000 developers

[fd9750]

Interesting reading but I would like to propose that Forth or its derivative "White lightning" should be included in the list. In the mean time it has become so obscure that most people don't remember it ever existed. If I ever see a piece of code I wrote in the derivative I am 100% sure I would not even remember how it was supposed to work.

[CPallini]

Uh!? No one fears the common business-oriented language? :-D

[kalberts]

You mean, fear of wearing down your fingers to short stubs?

[W Balboos GHB]

Selections seem to be from a bimodal distribution of respondents: Selections disdained because they take brains Selections disdained because they're :elephant:ing dumb and annoying Or, put another way, perhaps the two groups are those who code and happen to get paid for it and those who code only because they get paid for it.

Ravings en masse^

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

"If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010

[Peter R Fletcher]

After spending a little time investigating Lisp, many years ago, I concluded that a better name for it might be "Stutter", given the names of the many list manipulation operators. :)

[obermd]

TECO - built for string manipulations and was used for the first version of Emacs. Definitely a write-only language as there was an annual competition to see who could figure out what a specific TECO line would do to an arbitrary string.

[Mark Miller]

Years ago I wrote a front-end program in dBASEIII that generated AutoLisp scripts to manipulate AutoCad drawings. The engineers would provide a few dozen input parameters, the AutoLisp script was built, then AutoCad was fired up and produce the drawing for them. I remember spending lots of time counting parenthesis and certainly agree with another comment - LISP = Lost In Stupid Parenthesis. The end result worked really well, and I learned how to count really well.

Sincerely, -Mark mamiller@rhsnet.org

[sasadler]

I started assembly language programming in the late 70's but in the last 20 years in my career as an Embedded Systems Engineer (now retired), I saw no need to use assembly language in any of the products I worked on. C/C++ compiler tech for anything from an 8051 to a TI DSP generate excellent code that's relatively hard to improve upon.

[Mike Hankey]

Very true, I seldom use assembler, mostly c++.

I'm not sure how many cookies it makes to be happy, but so far it's not 27. JaxCoder.com

[OldDBA]

I still use TECO occasionally. Learned it in 1972. I sometimes wrote TECO macros to do a task and while I was waiting for it to finish, I could write a Cobol or Assembler program to do the same thing, compile it and run it while still waiting for TECO to finish. It was really easy to use for scripting when the amount of data was small.

[Deepak Vasudevan]

(V)isual (B)asic (affectionately called as Very Bad) should be having a distinguished position in the list though.

[Stuart Dootson]

[DXL](https://www.ibm.com/support/knowledgecenter/SSYQBZ\_9.6.1/com.ibm.doors.configuring.doc/topics/c\_dxl.html) is the worst one I've used... It's a pretty basic C-like language - the horrors come from the interface to the DOORS requirements management system, and how easy it is to leak memory without even trying. Here's [an example](http://www.smartdxl.com/content/?p=481) - DXL can allocate, but not *deallocate* strings, so every string you use takes up memory, until the process (which might be on the server side of DOORS) is terminated. I encountered DOORS and DXL when developing an API for accessing DOORS from Java, using (in-effect) hand-rolled RPC to call from Java into DXL (using a DLL written in C++ as an intermediary) and then returning results from DXL in JSON, which was deserialised into Java objects using [Jackson](https://github.com/FasterXML/jackson). Of this, two parts *didn't* suck - C++ and Jackson. But... it worked. And worked reliably.

Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p