The two first points don't have much to do with the "language" aspects of JavaScript itself or ES6. NPM (the registry) is simply the winner of a long-running l

The two first points don't have much to do with the "language" aspects of JavaScript itself or ES6. NPM (the registry) is simply the winner of a long-running low-intensity conflict to determine the canonical registry for the JavaScript ecosystem. Bower (the registry), is NPM's front end alternative. It is now almost irrelevant but its client essentially works just like the NPM client, installing whole packages and dependencies in `bower_components` (versus `node_modules` for NPM). Both clients let you choose where to put that directory and/or how to name it but you will undoubtedly end up with a lot of useless/potentially harmful files coming from dozens and dozens of untrusted third parties to manage in your `public` directory. That sucks hard. The only working solution to that problem is to use a bundling mechanism. You keep all your third party packages and their dependencies private as well as all your sources, and only deliver to the browser a couple of bundles that only contain what's strictly needed: `main.js` and `main.css`. But now you have to choose a bundler. And the module pattern you will use throughout your project. And the JS flavor. ES5 is no more broken than ES3 was and ES6 doesn't really fix anything in ES5. If you want to find something broken, take a look at the JS ecosystem instead. Hyper modularizing your code and juggling with `exports` and `require()` can be useful but it's definitely not the only way to write a working website.