Much faster if you are willing to punish your users for using subpar browsers that don't keep up with current technologies and standards.
A bullet I retrospectively think we should have bit a long time ago. It would have sent a strong message that you either make sure that your browser is top notch or it will be left behind to bite the dust of the power horses.
Now that Microsoft is feeling the heat under its ass (from FF, Chrome and Safari), they're making sure IE is not ridiculously worse than the competition, that it auto-updates, they're engaging the community, creating libraries, etc.
>Much faster if you are willing to punish your users for using subpar browsers that don't keep up with current technologies and standards.
Actually Chrome is a complete mess ES6 compatibility wise.
Most of the interesting stuff is unimplemented still, and what is there is hidden in options the user has to specifically enable.
Sure, the standard is (now) only due for 2015, but Chrome dragging its feet is also one of the reasons for that. And it's not like FF waited for the standard to be stamped and released to have the implementations according to the standard already working.
I can't even think about blaming my Clients for not using the latest IE because I want to use some syntax sugar for things that I can already do with ECMA 5.
That's not what I'm saying. I'm talking about 5 years ago when IE7/IE8 were lagging behind by a HUGE margin and it was another world trying to make things compatible. It was not a matter of using the last version, it was a matter of Microsoft not paying attention or not wanting to make its flagship browser better. Not just some developer throwing a fit because he needed "sugar".
Also, and that's only personal opinion, but there's a limit to the customer is always right. What if we create a new super highway one day with flying cars, are we going to punt on moving on because some people like their combustion engine pieces of junk? It's also our jobs to make people understand that jumping on the latest technology is in their best interest.
Leveling the field to the lowest common denominator brings everyone down in the end and really hampers creation and innovation.
And that is the reason why Javascript is so far behind modern languages in so many areas.
Nearly everything works in firefox. Most features exist in Chrome but are marked experimental and can be enabled by a command line flag (I think). If you're selling a continuous integration service to developers, you'll probably be perfectly fine using any of this in a year or two. If you're selling "how to use your email client" video lectures to the elderly, you might have to wait 10 years. There is no single "real world".
traceur-compiler can preserve ES6 syntax (without desugaring it), it's only missing automated feature detection at runtime (which I wanted to add more than an year ago, but was busy with other things).
A bullet I retrospectively think we should have bit a long time ago. It would have sent a strong message that you either make sure that your browser is top notch or it will be left behind to bite the dust of the power horses.
Now that Microsoft is feeling the heat under its ass (from FF, Chrome and Safari), they're making sure IE is not ridiculously worse than the competition, that it auto-updates, they're engaging the community, creating libraries, etc.