4 ms·
Not a React guy, but there is lot's of hyperbole in here. Not sure how npm, webpack, babel, "thousands of transpilers" et al slow you down. They're tools that
by 91bananas 10y ago
Not a React guy, but there is lot's of hyperbole in here.
Not sure how npm, webpack, babel, "thousands of transpilers" et al slow you down. They're tools that do things so you don't have to... Are you seriously saying that hand converting ES6/7+ to running ES5 would be faster than babel? Hand bundling/splitting of code would be faster than browserify, webpack? Hand finding, curating, tracking of dependencies would be faster than NPM? mmk.
- deleted 10y ago[deleted]
- kuschku 10y ago> Are you seriously saying that hand converting ES6/7+ to running ES5 would be faster than babel? No, that shouldn’t even be a thing. All runtimes, worst case, should be maybe 6 months behind the standard, otherwise I’d want to use a single transpiler. Going TypeScript -> ES7 -> ES6 -> ES5 is insanity. > Hand bundling/splitting of code would be faster than browserify, webpack? Why should that even be necessary? Upload your code file by file, and actually use the browser’s required, or have one single script implementing this as polyfill. Why should I even have to do this? > Hand finding, curating, tracking of dependencies would be faster than NPM? mmk. No, but NPM’s tracking is useless when dependencies constantly change their API with every release. I’ve got so many dependencies via NPM that even change their name and API constantly that many of my projects have been broken after just a year, but all after max 2 years. I’ve got Java projects that are 5 years old and every dependency is still update, with a stable API.