It's nice how you mentioned billions of dollars in the same sentence as v8. As if your assembly-run CPU would be magically faster running three damn gigabytes

It's nice how you mentioned billions of dollars in the same sentence as v8. As if your assembly-run CPU would be magically faster running three damn gigabytes of code in another language. JS isn't the problem. Babel is the problem. And every library using it, instead of using ES2020+ directly because every Browser supports it anyways. NPM needs an ESM modules based header files system, and packages should be not binary, not uglified, but maintained by a standard of expectations what a library can and cannot do. Split up header files, namespaces for definitions, and expected types for all functions. "Still using phantom? Sorry we block your package because it's outdated." "Compiling to es5 commonjs with ie6 setting? Sorry, your package is outdated." The ecosystem in JS has become a joke not because of the language, but because of the tooling. And now writing tooling in another language to replace that tooling will just end up in the exact same state all over again. For the love of Rust, please don't fuck up rust crates the way the Babel fatigued ecosystem did. Don't go the micropackage way, it didn't work and it's time to reflect on that, and build up a standard library in a more centralized way.