11 ms·
>Most language features, really. Name a few. >terrible "prototype" system >malice that is "this" It sounds like you are talking about ES5, not ES6+
by xamuel 8y ago
>Most language features, really.
Name a few.
>terrible "prototype" system
>malice that is "this"
It sounds like you are talking about ES5, not ES6+
- bitL 8y agoCan you guarantee all ES6- code to disappear immediately? Or are you forced to dive deep into warts when you have to work on some older JS project?
- jhall1468 8y agoWow, now we're complaining about the outdated versions of a language? Come on man. Nobody is going to write a modern application in ES5 and there are plenty of warts in old Java, C and Python applications as well. That's the nature of them being "old".
- shawnz 8y agoWhy does that impact whether or not it's a reasonable choice to use the language today? Old libraries I could understand, but old independent projects? How do they affect the current state of the language?
- bitL 8y agoIsn't it obvious? You apply for a job, company that isn't a startup has code that is likely written with old JavaScript whose replacement is not economical, so even if you do everything new in ES7, you still have to wade through old ugly code, likely everyday.
- StavrosK 8y ago> Name a few. He did, literally exactly after that sentence.
- xamuel 8y agoNo, he listed some things that he thinks are broken, he didn't list missing language features
- deleted 8y ago[deleted]
- StavrosK 8y agoI read it that he meant "fixes for these things are missing and that makes me hate it", i.e. I read it as the answer to your question. He doesn't hate it because it lacks features, he hates it because the existing features are badly implemented/thought-out.