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.
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.