Thanks for the explanation. I understand the rationale (if any), but the irritating part is when one sits down and tries to get stuff done. The mere fact that

Thanks for the explanation. I understand the rationale (if any), but the irritating part is when one sits down and tries to get stuff done. The mere fact that there are a lot of ways of doing something, with one tool having many variants, is a pain. I thought of pointing my NPM installs to a different folder, but that felt like a hack for something that should be simple. I tried out WebPack, but was getting silly errors that were leading me to keep on searching for solutions. I eventually just copied over the files that I need, and overriding 'require' with a function that returns null, just so I could at least get some stuff done without worrying about too much for now. I'll spend more time in the coming days trolling Github to see how some people are doing things. > 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. That's my feeling too, it's like we're creating stuff just because other languages have it too.