- make it easier to use multiple processors
- use a new type of DOM designed for web app GUIs which can be translated as necessary back to our current DOM
- have built in version checking for its interpreter/JIT
- make it easier to manage memory usage
- have a module system
- be highly specialized towards the web and web app development
- eg. built in language components that make communicating with the web server easier
- be easier to implement in the browser
I guess that if we want to have something after JS, that will come either with:
* more standardized languages, with native in-browser VMs, as Google is trying to do with Dart.
* get rid of the browser.
The latter is way more contraversive, but I like it nonetheless.
The less contraversive version is: the end of the browser as we know it.