New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Blog Post: Top 10 reasons to use 6to5 #25

Closed

jamiebuilds opened this issue Jan 9, 2015 · 2 comments

Labels

blog

Contributor

jamiebuilds commented Jan 9, 2015

I've been asked for something like this by a few people now.

jamiebuilds added the blog label

jamiebuilds changed the title ~~Top 10 reasons to use 6to5 blog post~~ Blog Post: Top 10 reasons to use 6to5

xfq commented Mar 31, 2015

Here are my reasons:

I can start using ES2015+ code today without waiting for browser support.
There is no runtime dependency.
Babel is available everywhere: Node.js, Meteor, Rails, Grunt, Gulp...
Babel (and JavaScript/ECMAScript) is constantly evolving.
The output is readable.
Every transformation can be turned off.
Babel has a REPL.
Babel supports JSX and React.
The level of ES2015+ support is ahead of most (if not all) of the alternatives.
The documentation is fantastic.

(Moreover, corporations such as Netflix, Yahoo!, PayPal, and SoundCloud are using Babel now.)

pavelthq commented Nov 3, 2015

What is a browser support for babeljs? I mean if I compile my code is it will work for example in ie9?

jamiebuilds closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment