1. My complaint is not about speed. 2. Node is much better than Python because the correct location on disk is pretty much project/node_modules. However, it is

1. My complaint is not about speed. 2. Node is much better than Python because the correct location on disk is pretty much project/node_modules. However, it is still that case that e.g. Babel was broken by Node 12.17.0 [1] last year, which necessitates something like NVM. I don't want to deal with that for my build tools. I just want a binary that is known to work to continue to work until it is replaced. 3. Yes, conventionally everything in Nodeland was written out to dist as ES5. This also sucks ass because now you end up shipping a bunch of ES5 crap to your end users even though you aren't targeting ES5. It is very hard to build an actual ES2020 module unless you're willing to not use external dependencies at all. Snowpack et al are shifting this slowly, but it has barely even begun as a trend. [0] https://nodejs.org/en/blog/release/v12.17.0/ https://nodejs.org/en/blog/release/v12.17.0/ https://www.google.com/search?q=babel+compat+data+corejs3+shipped+proposals https://www.google.com/search?q=babel+compat+data+corejs3+sh...