4 ms·
Javascript. Not to remove it, but to make it better from the start. Current JS feels painful to me because it feels like piling hacks on top of a poorly-designe
by notamy 5y ago
Javascript. Not to remove it, but to make it better from the start. Current JS feels painful to me because it feels like piling hacks on top of a poorly-designed language to make it palatable. Doing it better from the start sounds amazing.
- D13Fd 5y agoI'd give it a better name, which does not involve the word "java."
- creativeembassy 5y agoAnd ECMAscript still sounds like a disease.
- kzrdude 5y agolet's just pick a letter and it's fine. escript cscript mscript ascript
- pteraspidomorph 5y agoLet's face it, it would end up as "JScript". What we now know as "JScript" would probably become "MScript" or something.
- deleted 5y ago[deleted]
- FranchuFranchu 5y agoEcma balls
- ryall 5y agoBut it's such a great litmus test to instantly identify the people that don't know what the hell they're talking about ;)
- masswerk 5y agoThe original name was LiveScript…
- masswerk 5y agoThe thing I'm most offended with: about every generation has now dumped their favorite interface pattern onto it, mostly reused from the fancy language of the day. It has become a Frankenstein language without internal strictness or attitude (which had been once a major trait.) I guess, it's the language most disrespected by its developers.
- lowercasename 5y agoI'm OP, and this was in fact my response to my question! Everyone else is suggesting these wonderful grandiose economic and social changes, and I just want a strongly typed (or, hell, even a little bit typed) Internet...
- aaron-santos 5y agoI wish Brendan Eich's original intention to put Scheme "in the browser"[1] had succeeded. There was never any reason to invent a new browser language when perfectly good one's already existed. [1] https://books.google.com/books?id=3b40AwAAQBAJ&pg=PT32#v=onepage&q&f=false https://books.google.com/books?id=3b40AwAAQBAJ&pg=PT32#v=one...
- krapp 5y agoIt would have been nice if the original idea to have the web support multiple scripting languages had panned out. That's not a design problem, though - some form of code running in the browser would have been inevitable, and it was considered as a possibility from the beginning - but it seems inevitable in hindsight that one language would have won out and we would have all been stuck with whatever quirks and pecadillos that language had. Maybe if something like webassembly had come along earlier, we could have avoided all that "javascript as bytecode" nonsense.