>> If you do try modularize JavaScript, you're going to need a compilation chain to package it all together - so you're not getting away from that. That's not

>> If you do try modularize JavaScript, you're going to need a compilation chain to package it all together - so you're not getting away from that. That's not always the case on the front end (it's still possible to code on the front end without a bundler). And it's certainly not the case on the backend (I.e. Node.js). >> Sure it adds up, but it's a tradeoff. If you're writing a dinky little web app for your grandma, maybe that trade-off isn't worth it. This could not be further from my own experience having gone back and forth between JavaScript and TypeScript multiple times both professionally and as part of my open source work for over a decade. I've built highly complex scalable distributed pub/sub systems, P2P systems, blockchains and a decentralized exchange using plain JavaScript in record time with no bugs found for over a year.