3 ms·
If we "move away" from Javascript, we also "move away" from being able to properly support and display much of the web in the future. We can either discard the
by krapp 10y ago
If we "move away" from Javascript, we also "move away" from being able to properly support and display much of the web in the future.
We can either discard the current web as obsolete and start over with a new, stricter or more elegant framework, or else support something alongside Javascript, which only compounds the problem when every new browser then has to support every web language, and older browsers can no longer run code written in the 'new' languages.
To say nothing of the likelihood that each language will have browser-specific implementations, so each language also gets its own unique ecosystem of frameworks and shims for cross-compatibility.
All this towards the same end of doing stuff with the DOM, AJAX and Canvas. Doing what you can already do in Javascript, despite its issues. Why? How does it help the end user?
Javascript may be bad, but the alternatives seem to be worse for everyone other than programmers who don't like Javascript.
- symboltoproc 10y agoWASM will become available on every major browser and there will be ways to backport the code to older browsers (i.e ASM.js or polyfilling). There are also multiple implementations but the community is not split into different ecosystems. Why do you think this is not possible again?
- krapp 10y agoI don't think it's impossible, I just think it's not worth the effort. Other languages won't add any functionality that javascript doesn't already provide, or that isn't already served by languages compiling to javascript. It only adds unnecessary complexity to an already messy ecosystem.