3 ms·
The past year or so I've moved almost exclusively to backend at work (from Vue frontend) and simultaneously switched to vanilla JS for all new side projects. Fo
by anderspitman 6y ago
The past year or so I've moved almost exclusively to backend at work (from Vue frontend) and simultaneously switched to vanilla JS for all new side projects. For those I use native ES modules heavily for internal code, and use very few external dependencies and import them as global scripts like a heretic. Heck I often don't even use npm for node projects anymore.
For my latest project I'm even trying to make the entire interactive UI without any JS. I've sadly never done this.
The sense of relief getting out of "modern" JS has been palpable. No more build steps. No endless dependabot PRs. No painful dependency updates. Just good clean fun development.
There are tradeoffs. vdom frameworks really can add a lot of productivity vs hand-coding dom updates. But if I really need it I can use something like Mithril which still doesn't require a build step.
- nwienert 6y agoAscetics brag about asceticism, vegans brag about veganism, the world turns. Didn’t the Buddha already teach us about the middle way?
- anderspitman 6y agoBuddhists brag about Buddhism
- sebmellen 6y agoTurtles all the way down
- manigandham 6y agoWhy not just stick with Vue then? It runs with a script tag and no build step, and works with HTML templates by default.
- aniforprez 6y agoPeople tend to recommend alpinejs for very light js interactivity without a full framework. The tailwind folks use it a lot
- qudat 6y agoFor personal projects that I'm not certain are going to require a battle-tested, fully capable of handling any weird business requirement from product, I always start simple. This strategy has worked great for personal projects. However, I would never start this way for a commercial product.