3 ms·
It's probably less to do with a bytecode 'standard' vs. a set of standard libraries for doing things outside of the browser (file manipulations, etc). Then brow
by pyre 16y ago
It's probably less to do with a bytecode 'standard' vs. a set of standard libraries for doing things outside of the browser (file manipulations, etc). Then browsers could just not support those libraries, but JavaScript VM developers could. In this way, it would be possible to not have 'the future of JavaScript' tied down to a specific bytecode implementation. Then people could pick and choose the VM that they want to run their JS in based on what sort of optimizations they needed.
One of the largest requirements here would probably be a method of linking against/using C libraries, and also a standard for 'import/#include/etc' statements.
Maybe I'm being naive here though. Feel free to correct me.
- SudarshanP 16y agohttp://code.google.com/p/nativeclient/ http://code.google.com/p/nativeclient/ may answer your need. Hopefully someday something like this will be available cross browser...
- pyre 16y agoI'm not talking about pulling C libraries into the browser. I'm talking about expanding the use of the JavaScript language outside of the browser (beyond even something like Node.js). Unless I'm completely misunderstanding NativeClient, that's not what it's about.
- known 16y agoDoesn't both merge at some point?