I've been curious about why we haven't seen a legitimate replacement for JavaScript in web browsers, despite the existence of languages that compile to it. I get that JavaScript will likely be supported for the foreseeable future and that there's no shortage of languages like TypeScript or Kotlin that compile into JavaScript. But shouldn't there be a more universal approach, like a generalized virtual machine that all languages could target for browser-based operations? I know WASM is around, but it has its own limitations and still runs in the context of JavaScript. Working in mainframes, I've noted how we can use various languages like JVM languages or Go. It seems that the issue lies more in the politics of getting a new standard agreed upon across different browsers rather than purely technical barriers. I'm wondering if there are any technical reasons holding us back from a proper alternative to JavaScript?
1 Answer
It's definitely a complicated situation. Any new language would need to be universally supported on day one across all browsers. If it only works in one or two browsers, developers won't bother using it, and it's risky for newer languages without guaranteed support.
It seems like there's a lot of history on this, especially with Flash and Java Applets. Those were never integrated deeply into the browsers because they relied on Chrome and IE, and both ended up becoming proprietary. They couldn't compete with JavaScript being an open standard.