(Obviously C can't be that language for the web (NaCl possibly excluded), but when I say C, I mean in the general profile: extremely simple and maps very closely to what the hardware is actually doing)
(Obviously C can't be that language for the web (NaCl possibly excluded), but when I say C, I mean in the general profile: extremely simple and maps very closely to what the hardware is actually doing)
1. Bytecode formats are never completely language independent - there's always a feature or change that would make language X better
2. Browser vendors will never be able to agree on a bytecode format
So, to solve those problems, I've been thinking the following approach might work:
1. Write a JavaScript interpeter for a fairly language-independent bytecode
2. Write some small languages, targeting that bytecode (something for everyone: Haskell-like, C-like, Lisp-like, Forth-like, etc)
3. Hope people start writing more languages to target the bytecode
4. Hope that it's hard for browser vendors to ignore implementing the bytecode natively - for performance reasons
This way we avoid committees and just get it done. Let me know if you think this is a good or bad idea. I'm very willing to work on it.
Moreover, it’d be trivial for browser authors to implement, so for a very low investment there could be a huge return. You can write a basic runtime for a full-featured concatenative language in a few hundred lines of C, and a compiler for it in a few dozen lines of Haskell.
My bet would be a minimal standard library, based on empirically most useful functionality. I very much doubt you'd need more than a thousand lines to implement that (not counting a possibly crap-load of optimizations).
Though I wish I didn't have to type `from datetime import datetime` all the time...