I know I'm far from the only one but I just wanted to throw out there that my company is now using babel to transpile our ES6 to ES5. The conversion (which only touched the code we've written in the last year or so b/c the old code is just spaghetti so we only converted what was already JS "classes") took less than a week of 1 dev's time and has been flawless so far (been using it production for a little over a month now). We are using gulp to facilitate this process. Just wanted to add a data point to those considering using it.<p>I've found the JS to be much cleaner and easier to read and I've heard similar statements from the rest of the dev team. I highly recommend it. The best part is you can convert your code 1 file (or "class") at a time and your old JS will still continue to work perfectly.<p>Feel free to ask me any questions about the process and any potential issues and I can respond with how we dealt with it (if we did).
Wow Spartan (IE replacement) is really kicking some major ass with its ECMAScript 6 support:<p><a href="https://kangax.github.io/compat-table/es6/" rel="nofollow">https://kangax.github.io/compat-table/es6/</a>
Babel contributor here. It's great to hear how many people are already deploying projects using Babel, and even better to see how fast ES6 is getting adopted. Many people are still stuck in an ES3 world... (<i>shakes head</i>)<p>If anyone has any questions, feel free to ping me or stop by our support chat[1].<p>[1] <a href="https://gitter.im/babel/babel" rel="nofollow">https://gitter.im/babel/babel</a>
This states TypeScript is layered on top of ES6. I did not believe that to be true. Is there some meta-bug or other location tracking the TypeScript move to ES6? I was under the impression there were still a number of bugs that prevent fully using TS with ES6. (Maybe I'm wrong and someone can fill me in :))
If you're looking for a ready-made template project to try out ECMAScript 6/7/2015, I created, and have been successfully using my base-node [0] and base-angular [1] projects for a while now.<p>You can use babel or traceur (just comment/uncomment one line), although the default is traceur. Gulp is used for building, packaging, and lint/transpile on save. base-node contains everything to package your application into a minimal Docker container (<10MB compressed + your minified, transpiled code) with io.js. base-angular will give you a module system, LESS transpiling, live-reload (LESS/CSS changes are injected without reload), and a minified, cache-busted output that you can drop into any web server (minimal nginix containerization in the works).<p>I'm sure the documentation could be better, but the Readme.md has enough to get you started and the code should be very straight-forward.<p>Since I'm using git, I can set these master repos as the 'upstream' and whenever I make changes to the base project (like, adding containerization support) I can easily push that change out to all my projects and everything gets tracked nicely in the revision graph. The `create.sh` script in base-node will actually do that rewiring for you.<p>[0] <a href="https://github.com/blakelapierre/base-node" rel="nofollow">https://github.com/blakelapierre/base-node</a><p>[1] <a href="https://github.com/blakelapierre/base-angular" rel="nofollow">https://github.com/blakelapierre/base-angular</a>
Not a fan of transpiling; you go from having one language to having to understand two (ish; ES6 isn't entirely different) while only being able to debug in one. It's nice people can write in and actually use ES6 today but I really don't think transpiling is worth it. I've been bitten by weird bugs in transpilers before that wasted far too much of my time.<p>> npm may eventually support two versions of the same module, which would enable you to deliver libraries as both ES5 and ES6 for Node.js, io.js and client-side module systems that are based on npm.<p>No, please no. Why would I ever want to deliver a library in both modes just for some better / different syntax? Yes ES6 is nicer than ES5 but doubling the modules isn't worth it at all.
Switching from writing classes in other languages to using the JS prototype made writing object oriented code more fun and much faster! The prototype way was a step forward. I think it's very weird that JavaScript is now planning to introduce classes, and that you guys are so exited about it.
If I just want to clean up some basic code in a .html file with a terminal script - preferably with a "--watch" flag, what's the simplest way of accomplishing that?<p>Also seems like the best way to ease into it.