Erez Schatz

Those are all secondary reasons and are equally shared by many other languages, some of them more successfully yet no one shares JavaScript's dominance because only JavaScript runs in the browser.
That's it, reason no. 1-10. JavaScript runs in the browser. You don't need an interpreter, compiler whatever, got a browser? Got JavaScript. Wanna build a site? learn some js. Want to use a frontend framwork? It's JavaScript.
Reason no. 11 is node.js which allow frontend devs to transfer their skills to server side, so they don't need to learn a second language.

The whole "green on black" theme is yet another example of how cargo-cult people are. The "x on black" display was created to save resources during the almost primitive days of computing, and this was the most cost-effective way. Using a terminal on a GUI today, the OS draws the whole window regardless if it's black on white or white on black. So it leaves us with the question of whether either is "better". There's no evidence that either is, but, since most of the other applications, like the browser is using a light background, switching from it to a dark background is forcing the eye to constantly refocus. And using "dark mode" isn't really a solution, you can't "dark mode" the sites, or your office documents, i.e. the content, just the chrome. The best solution is using a soft, pastel colour as background and black characters in front. But I guess it doesn't look cool enough. And speaking of which "I think it looks really cool at night."yes, it is. And 30 years from now, you'll live to regret that thought. Turn up the lights.