> it’s been damaged way too much already Why? It's one of the most comfortable languages for me. Some parts of it are objectively bad, sure, but why even touc

> it’s been damaged way too much already Why? It's one of the most comfortable languages for me. Some parts of it are objectively bad, sure, but why even touch those parts when the language constantly gets updated and modernized... I'm saying this as a developer who mainly writes C# and Go these days. With JS, without dabbling in wasm wizardry, I can open a console in the browser and directly get an environment with crazy interaction possibilities. If I'm writing something for the long run, I can use a lighter compile-to-JS language like Typescript (my fav) and when there's an error, I can directly map what's going on to actual source code without even using source-maps. In addition to that, admittedly like many other languages, I can write 2 lines of it in a file, double click the file, and have a web server running! It's amazing that JS gets more and more love, and there are many of us caring for it. The whole rhetoric that "JS is bad" is getting old. People talk down JS then start using others where white space count matters... Yeah it's all preference but that is my point as well. If you don't like JS direction, you can use your favorite lang via WASM, and let JS get developed in a faster pace as well. So TL;DR: Why not think the other way around the issue!