4 ms·
If you're still whining about the "JavaScript Problem" in 2015 without trying ES6, it's going to be hard to take you seriously.
by izolate 12y ago
If you're still whining about the "JavaScript Problem" in 2015 without trying ES6, it's going to be hard to take you seriously.
- Zikes 12y agoThe "JavaScript Problem" is not about what JavaScript can or can't or will be able to do, it's about JS being the only option available, period. The web needs a bytecode language that other languages can compile to. Some people say JavaScript can be that bytecode, and asm.js is a big step in that direction, but for the web to grow to its full potential developers need the freedom to express their ideas in the languages that suit them best.
- tracker1 12y agoWith the number of languages that transpile to ES5 or asm.js, I don't think that's really the problem.
- steveklabnik 12y agoES6 doesn't exist anymore, it's ES2015 now.
- angersock 12y agoReally? That's...silly, I guess?
- steveklabnik 12y agoEh. I feel pretty neutral about it. It seems to reflect the mentality of shorter, more frequent updates to the language. Nobody wants another loooooooong wait like the current one.
- izolate 12y agoI know. But my comment was directed at OP, who seems pretty unfamiliar with JS, and would more likely know what ES6 is. Also, I didn't want to write "2015" twice.