3 ms·
The aversion to build tools is strange to me, for two reasons: 1) The pain points usually come when you're configuring things from scratch. If you're always do
by brundolf 6y ago
The aversion to build tools is strange to me, for two reasons:
1) The pain points usually come when you're configuring things from scratch. If you're always doing solo greenfield projects, you can just carry around a boilerplate project and you should be able to largely avoid messing with configuration after the first time
2) "I optimize for performance and quality" Well, doing a JS build can help a lot with asset size and therefore performance, especially compared to doing a transpile at runtime which is what it sounds like this person is doing instead
- pjmlp 6y agoWell, I write vanila.js, place the JavaScript files into /scripts folder and the JEE, ASP.NET build does the work for me. Zero worries about npm, node, babel, whatever is the tool of the day. Working today, just like 15 years ago.
- brundolf 6y agoBabel has been the "tool of the day" for 5+ years. Node/npm for closer to 10 years. And if you version-lock your dependencies - advisable for anything you're handing off to someone else - the same config + dependency version isn't going to suddenly break for no reason down the line. It's an unfounded trope that things are otherwise.
- pjmlp 6y agoDifferent strokes for different folks.