hello fellow anons, textboard newbie here. i'm here to ask a very important question: what do you all consider to be the worst programming languages?
PHP
>>2
For as bad as the lack of language design (or lack thereof) in PHP is, I can't bring myself to hate it. It gets things done, it has widespread adoption, and life could be way worse.
I have a hard time hating any language for long... unless I have to use it :D
The monster that is C++ ?
there isn't one, there's just undisciplined people, who like to mask own failures as professionals behind adhoc fault analysis at best and community consensus at worst
>>6 truth
Define ‘worst’.
Depends on the use case. Javascript is one of the worst programming languages for big safety-critical real-time systems. It is one of the best for web frontends. Ada would the opposite.
You can't. For most situations, it would have to be assemblers, because they lack any quality you would want to see in clean and well written programs. But if you have to work on that level, you don't get the choice.
COBOL
>>1
Just don't ask, OK? Just ignore the bad languages. That's it. And asking for best languages is not any better. It doesn't really matter which you use. So long as it doesn't suck, which can often be precisely approximated by finding out what iss well-regarded in the industry, and has worked well for the past few decades.
If you're a neophyte, you don't need to be immediately up-to-date with new research. Stick with what works.
If you're already an expert, you know how to find out on your own, or with the help of a few colleages.
Specifically for software producers (intentionally using the generic term), it's important to understand the mathematics, i.e. the systems (turing machines and lambda calculus, data structures and algorithms, computational complexity,,), and basic style that doesn't suck.
That's all you have to do if you're a neophyte: make sure that you don't suck, and that what you make doesn't suck. Once you understand the basic stuff, you'll know how to get to the excellent stuff.
Of course, for "extra credit", you can study the mathematics intensively. i.e. from one of the foundations (e.g. Category theory or Class theory), building up rigoursouly, by exercising utmost skepticism at each step of each proof, thus ensuring each that theorem is proven; and creatively, by going through a series of poof-sketches, and filling it the details, guided rediscoveries where the course lays hints that imperceptibly get sparser, until the student is rediscovering the proofs of various known theorems, until the student is rediscovering known theorems (and their proofs) with no guidance, whence he can start (graduate school, after which he can start) to do original research.
The intensive mathematical approach is better, because it ensures that, at all times, if you are doing something, you know exactly what you are doing. And if you don't know what you're doing, You first figure everything out, before doing anything.
Take the top 1% of anything. All of it is going to be so good, that the difference between the one at the very top, and the one at the bottom of the 1%, is small enough that the difference may as well be noise: as meaningless as the shush of the transceiver at vacant radio frequencies.
Of course, you might nbe interested in such a question if you're an expert, or a mathematician. If you're mathematician, you'd just read the relevant research paper, or do the research yourself, or with "a few" colleagues. If you're an expert, you'd just read the relevatn research paper, or figure it out yourself, somehow, or ask other experts. Any good expert knows how to identify experts in the same, or similar field.
You certainly woudn't ask the way you asked. you would describe the state of your knowledge, and questions whose answers you may be seeking.
Even if you were a neophyte, you'd better first ask your superiors (e.g. bosses, professors), or your peers, or, rather, persons whose level is a bit above your level (e.g. colleages that understant the way things are done, who can give suggessions based on that; colleages whose skills is slightly better than your skills, whose suggestions might go against the usual way things are done, but are better suggestions; students of higher grades)
The only remaining possibility is tht you are free. (i.e. No work, no boss, no school, no professor,,) If that's the case, do a basic web-search before you ask someone. If you've done the web-search, and you didn't find exactly what you need, then you can probably compile everything that is almost what you need, and sift through it, puzzling it out. Of course, at that point, you are either asking a question that has yet to be answered, in which case, your becocming an expert would get you an immense benefit, or you are asking a question that is answered, but you didn't recognize the answer in your web-search, because it was formulated in such a way that only persons familiar with the topics would be able to recognize it as an answer to that question.
>>12
If still you want my opinion, the worst programming language is idiomatic english.
There are two languages that have always horrified me: Forth and Tcl. I'm not sure how rational it was, but even hearing their name made me feel uncomfortable.
Scheme
Serious answer: Mumps. It makes PHP look like Agda.
>>16
I've never heard of it. It's still in use in hospitals systems according to Wikipedia.
s A="String" F i=1:1:$L(A) W $c($S($A($E(A,i))<91:$A($E(A,i))-52#26+65,1:$A($E(A,i))-84#26+97))This looks like a perfectly fine and readable ROT-13 function.
...looking back this was a shit question to ask
>>17
It really could be confused with "Hello World" in Malbolge
(=<`#9]~6ZY32Vx/4Rs+0No-&Jk)"Fh}|Bcy?`=*z]Kw%oG4UUS0/@-ejc(:'8dc