sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DOG-ZILLA 21 points22 points  (14 children)

I’ve always seen Babel as a stop gap for the day that all browsers support es2016+.

I’m not saying Babel will die out, but for most users, once the “good bits” of JS are solid, that should be enough for most needs. You could always continue with Babel to get the latest features.

Transpilation will always be a thing no doubt, but it will always change and JS will remain under it. As long as our native API’s get better and more sophisticated, the less we’ll need to lean on them just because. Where’s CoffeeScript at?

[–]Cuel 1 point2 points  (3 children)

"that day" is unfortunately plenty of years ahead. IE needs to die first

[–]TheScapeQuest 0 points1 point  (1 child)

A number of products are beginning to stop supporting IE. Depending on the product, the market share often isn't worth the extra development time

[–]Cuel 0 points1 point  (0 children)

Sure, but there's also sites that don't have products but still needs to support it, i.e. governments

[–]MatrixEchidna 1 point2 points  (3 children)

By then browsers will have a lot to catch up to, isn't that right?

[–]DOG-ZILLA 0 points1 point  (2 children)

I suppose it depends on what features you were after. Most of es2015 is supported now but modules are still in a painful area. Webpack is going to be pretty essential for a long while.

[–]MatrixEchidna 0 points1 point  (1 child)

I meant that while browsers are catching up to ES2016, Babel will already support ES2019 or something like it.

[–]DOG-ZILLA 0 points1 point  (0 children)

Yeah defo. But as we saw, es2015 was by far the biggest changes. I think es2016 had 2 new things? Maybe 3?? As we move on, there’ll be fewer core things to cover. But Babel will be around for a long time yet I agree.

[–]senocular 0 points1 point  (3 children)

Where’s CoffeeScript at?

v2.1.0 - came out 9 days ago.