[user3939382]

Your point touches on the hardest part of solving the problem. Even if we could all agree that JS needs to be replaced, which of course we can't, and we had a perfect ideal replacement that we all agreed upon, that already works -- what about the ecosystem? All the tutorials, videos, articles helping newcomers, all the libraries, linters, IDE integrations, build tools, etc.

The only way I can see the problem (assuming someone agrees it is) of JS getting solved is if something comes along that's so amazing and blows it out of the water so hard that adoption explodes and browsers start natively migrating to it, along the lines of what we've seen with TypeScript, but instead of a bandaid a full replacement.

[zanethomas]

I would be very unhappy with a suggestion to replace javascript. I like that I can mix functional, object-oriented, and procedural type code where each seems to be the best fit.

If something else comes along, gains a lot of traction, and develops its own ecosystem then javascript could conceivably eventually just fade into the background. But that's going to take time.