4 ms·
"It's going to take way too long to get these fixed to the point that we can actually start using new versions of Javascript because of slow browser adoption."
by Joeri 15y ago
"It's going to take way too long to get these fixed to the point that we can actually start using new versions of Javascript because of slow browser adoption."
Which isn't true, because you could compile newer versions of javascript to older versions. I see languages like coffeescript as interesting experiments in how the language can evolve, but eventually it needs to come back home to javascript and get deployed natively in browsers.
- BasDirks 15y agoSeeing how a handful of ideas in CoffeeScript have been rumored to be included in the next JS release, it seems like individual experimental language design might be the way to push for change.
- petermichaux 15y agoYes but many of the ideas in CoffeeScript were likely slated for ES.next before CoffeeScript. So it has been working in both directions.
- bgrohman 15y agoGood point. I hadn't thought of compiling old versions of javascript to new versions - that keeps everyone writing in the same language and seems like a better solution to me.
- petermichaux 15y agoThere was an ES4-to-ES3 compiler. The Traceur compiler takes many of the Harmony ideas and compiles to ES3.
- bgrohman 15y agoOops, meant to say "compiling new versions of javascript to old versions", not the other way around.