5 ms·
For a side-project of mine, I decided to not use babel (or typescript or any transpilation at all), and I've got to say, post-babel life is awesome. Sure, you'r
by roblabla 9y ago
For a side-project of mine, I decided to not use babel (or typescript or any transpilation at all), and I've got to say, post-babel life is awesome. Sure, you're limited in browser support. But it makes life so much easier, iteration time so much quicker, and we've got most of the es2015 goodies in browsers nowadays.
Being able to do the same on the backend side would be nice.
- qudat 9y ago"But it makes life so much easier." Is this because you don't have to install a plugin for every thing you want? I found both babel and typescript to have a learning curve and a configuration step that required dev cycles being spent on getting it to work properly. It really wasn't much of a difference in terms of getting things up and running. Typescript has plenty of weird nuances and configuration settings that are required to get things working properly, just like babel.
- joshuahutt 9y agoIf you're not using HMR and you're worried about iteration time, you're missing the biggest win. The time it takes to transpile a function is negligible. http://matthewlehner.net/react-hot-module-replacement-with-webpack/ http://matthewlehner.net/react-hot-module-replacement-with-w...
- roblabla 9y agoYou don't need babel to get HMR.
- deleted 9y ago[deleted]
- krainboltgreene 9y agoBrowser support is literally the tip of the iceberg.
- amake 9y agoWhat literal iceberg would that be?