Explain pros/cons of “no runtime” in README about babel HOT 4 CLOSED

If I understood it right, 6to5 doesn't require loading any JavaScript in your project (browser or node) to operate. It generates pure ES5 code which can run in environments that do not support ES6 yet.

For example this ES6 code will get converted to the following code that can run in Node and browser without requiring --harmony in Node or ES6 flags enabled in the browser

ES6

let arr = [1, 2, 3].map((item) => item * item);

generated ES5

(function () {
  var arr = [
    1,
    2,
    3
  ].map(function (item) {
    return item * item;
  });
}());

from babel.

@mohsen1 If it’s “that easy” to transpile ES6 to ES5, why does Traceur require a 75KB runtime to do the “same thing”. That’s what I’m trying to understand. I’m assuming there’s some advanced stuff in those 75KB that 6to5 is lacking, hence my inquiry.

from babel.

Traceur includes a mess of polyfills and emulates modules with a loader, store etc so it has to include a runtime because of these requirements. You can see an example of the fully built runtime here.

from babel.

Looks like, it’s mostly polyfills. Ok then.

from babel.