babel

It even allows your config to depend on a preprocessor (like Babel or CoffeeScript, see [1]).

However, people want to do much more complex apps with Javascript without having to mess around with Typescript, Babel transpiler, etc.

Not one browser implements TCO, and Babel only implements direct recursion, not mutual recursion.

Or use: myMethod = (arg) => {return this.value + arg;} With es7.classProperties in babel.

The goal of the Library of Babel isn't to be a perfect key-value store, just to create all the permutations possible within certain conditions.

It's really cool; it runs ES6 compilation with Babel (or Traceur) in the browser, and is able to download arbitrary versions of dependencies off a CDN.

All this time I've just been using a boring old shell script that runs browserify with the Babel plugin, and then uglify.

I've been using babel + browserify and leaning on whatever shims it provides...

I feel a new Tower of Babel collapse will come because technological change will outpace the rate at which human brains can learn.

I can share similar documents via org-babel, iPython notebooks, or Matlab notebooks, etc...

How does Babel compare to Traceur from Google?

Last time I used webpack, it wouldn't allow me to use ES6 CoffeeScript or JS code without using babel to downgrade to ES5 spec.

I hope it can work with "babel-node" without any hiccups, so I can keep my server on ES6.

Today I use babel to "transpile" es2015 to es5 and then load those in, could I do something similar with clojurescript?

Babel-17 and Empire Star are both excellent and were the first things of his I read.

I prefer the Book of Sand, which collects an infinite selection of the most legible pages from the Library of Babel.

Babel I have to use because all browsers struggle with ES2015 to an extent.