The 10 most dreaded programming languages, according to a survey of 65,000 developers
-
Stack Overflow, a popular Q&A site for developers, surveyed 65,000 users about the programming languages they use, and which ones they have no interest in continuing to use. The 10 most dreaded programming languages, according to a survey of 65,000 developers[^] I can think of worse!
I'm not sure how many cookies it makes to be happy, but so far it's not 27. JaxCoder.com
-
APL (a write-only language) Lisp (lotsa incredibly superfluous parentheses) Python (significant white space X| ) I actually enjoyed programming in Assembly (25-35 years ago)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
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
-
I stated out doing Assembler on the Apple II in 84 an I really liked it at the time. Then I taught myself C and after that didn't do much Assembler. Do some now on Embedded stuff, but not a lot.
I'm not sure how many cookies it makes to be happy, but so far it's not 27. JaxCoder.com
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.
-
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.
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
-
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.
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.
-
Stack Overflow, a popular Q&A site for developers, surveyed 65,000 users about the programming languages they use, and which ones they have no interest in continuing to use. The 10 most dreaded programming languages, according to a survey of 65,000 developers[^] I can think of worse!
I'm not sure how many cookies it makes to be happy, but so far it's not 27. JaxCoder.com
(V)isual (B)asic (affectionately called as Very Bad) should be having a distinguished position in the list though.
-
Stack Overflow, a popular Q&A site for developers, surveyed 65,000 users about the programming languages they use, and which ones they have no interest in continuing to use. The 10 most dreaded programming languages, according to a survey of 65,000 developers[^] I can think of worse!
I'm not sure how many cookies it makes to be happy, but so far it's not 27. JaxCoder.com
[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
