I'm gonna go use JavaScript, then.

Instead, they introduced generics, right, which is this huge, massive, category-theoretic type system that they brought in, where you have to under[stand] – to actually use it you have to know the difference between covariant and contravariant return [and argument] types, and you have to understand why every single mathematical... [I tail off in strangled frustration...]

And then what happens on mailing lists is users say: "So I'm trying to do X." And they say: "WELL, for the following category-theoretic reasons ...there's no way to do it." And they go: "Oh! Oh. Then I'm gonna go use JavaScript, then." Right?

Look, somebody spent a lot of time developing those theories.  You owe it to them to muddle through with whatever language they come up with.  You should be ashamed to still use a system so primitive as to just do what you tell it.  How will those poor professors get their next grant approved if you don't at least pretend their work is helping you?

Who in the world uses JavaScript nowadays, you morons?
I want to ask them, "do you REALLY want to go use JavaScript?"
I want to interrogate them. I want to interrogate them for roughly an hour.
Are you sure you don't just want to try saying "JavaScript"?
Coming from a dynamic language veteran such as myself, the latest trend among us vets is this, LuaJIT.
That's right, LuaJIT. This is the vet's way of programming.
LuaJIT uses trace compiling to avoid redundant table lookups. But on the other hand the cache coherency is a tad lower. This is the key.
And then, it's fast. This is unbeatable.
However, if you use heavy polymorphism then there is danger that you'll trip the guard and bail a lot; it's a double-edged sword.
I can't recommend it to amateurs.
What this all really means, though, is that you, >>1, should just stick with LISP.

JavaScript is a fine if imperfect language. That is all.

>>4
LuaJIT uses trace compiling to avoid redundant table lookups.
#red herring

Ya, somewhat newfag to /prog/ here, though not to programming.
But Idk wtf you guys are goin on about.
I use JavaScript making websites, jQuery, that shit is awesome.
What's your problem with JavaScript bro?

javascript > lua. last I checked lua wasnt, like, everywhere. And also is kludgy.

posts >>8-9 seem to have been deleted? wth? first time i see
moderators delete posts... kinda makes me wonder about all the
SPAM... wait a minute.... were those plentyoffish.com spamposts?
maybe there is moderation on /prog/?

>>7
perhaps people were referring to some of the nastier aspects of javascript.
http://blog.jgc.org/2009/09/javascript-must-die.html

also, nowadays people using javascript on the backend that is just silly... Node.js must burn and be replaced with LISP

>>11
In case you haven't noticed JavaScript is industrial Lisp.