Go and Erlang (or Elixir) both have a better async model, and are pretty much better designed on all points. So for the rare cases where async does matter (and

Go and Erlang (or Elixir) both have a better async model, and are pretty much better designed on all points. So for the rare cases where async does matter (and they are a niche, given even big names like facebook code behind async proxy and do long polling), there are still little reason to choose JS. I can't think of a single mission where, if I were not being forced to use it, I would chose it over something else. And I say that while coding a LOT of JS all year long. Even training people regularly in the language. I double down on my initial statement, if tomorrow JS is removed from the browser, it would die in a few years. It's a badly designed language that has been accumulated fixes over the years to make it acceptable while never removing what's bad. It was so initially bad that half the ecosystem of JS exists to not code in JS (typescript, coffeescript, babel, jsx, webpack...). And it has received that much of attention because we had no choice. Google spent millions to make a technical marvel of a JIT to run it at decent speed. Any tech that would have had half the resources poured into it would today be the incarnation of skynet. It's a language surviving on artificial life support than can do so because it has the best blackmail game of all time.