4 ms·
How are you really going to make substantive improvements without breaking a lot of things, or basically making it into a different language? Seems like there
by ilaksh 15y ago
How are you really going to make substantive improvements without breaking a lot of things, or basically making it into a different language? Seems like there is a limit to what you can do. Maybe they can add a few optional things, like require. (Fast forward to 2014: Oh, sorry, Internet Explorer doesn't support require, app won't run). Maybe all of these geniuses should stop and instead come up with a way to get rid of Microsoft or Internet Explorer. That's the real problem. Just kidding (sort of).
As long as CoffeeScript still works in the next major version of JavaScript, I will be fine.
- ZenPsycho 15y agoBy using a coffeescript approach of ES.next to ES.prev compilation. There are several such compilers already, including one from Google called Traceur, and the one as old as Javascript itself, Narcissus. They have been using Traceur and Narcissus for something like "reference" implementations of ES.next, to try out how features work before adding them permanently to the spec.