Modern JS is fine. It suffers from a lack of integer types and every method being dynamic dispatch is something runtimes have to optimize around, but the base language is quite nice.

Culturally JS doesn't have a tradition of libraries with deep inheritance hierarchies so you aren't wasting a bunch of memory, and cpu, constructing layer upon layer of useless base classes. This is an improvement over both Java and some C++. This also means the GC doesn't have to work as hard.

> Culturally JS doesn't have a tradition of libraries with deep inheritance hierarchies so you aren't wasting a bunch of memory, and cpu, constructing layer upon layer of useless base classes. This is an improvement over both Java and some C++. This also means the GC doesn't have to work as hard.

No it doesn't, but instead it has normalized using a ton of third party packages even for as silly as left-pad [1] that might take your whole application down, put the security of your users in jeopardy or even take bulk of JS built websites down [1]. Even if the left pad incident is excluded, everyday, JS developers rely on unaudited third party libraries from the shitstorm that NPM is. So, you just offset the library problem, not really solved it.

[1] https://en.wikipedia.org/wiki/Npm_left-pad_incident

Those are hardly the only two issues modern JS suffers from.