6 ms·
Perhaps the most significant thing is what he glosses over in this parenthetical paragraph: (Of course there is one way to support all the things at maximal sp
by stcredzero 14y ago
Perhaps the most significant thing is what he glosses over in this parenthetical paragraph:
(Of course there is one way to support all the things at maximal speed: Use a native platform as your VM. x86 can run Java, LuaJIT and JS all at maximal speed almost by definition. It can even be sandboxed in various ways. But it has lost the third property of being platform-independent.)
The argument is made that any bytecode is probably going to have most of the flaws of Javascript anyhow. However, it's a long standing truism that most problems in Comp Sci can be solved with another level of indirection. The TAOS VM was a virtual Instruction Set Architecture which could be Just In Time translated to a real instruction set architecture and run as fast as it could be read off disk. Since it is not a real ISA, it would also be platform-independent.
http://www.uruk.org/emu/Taos.html http://www.uruk.org/emu/Taos.html
Using such a VM would truly allow one to support any language on the web, at something like 80% "native" speeds. NaCL, LLVM, or even ASM.js could be grown into such a VM.
Additional levels of indirection are apt to create problems as well as solve them, however. Such an undertaking as an overarching standard would be very complex -- so much so, that it may never come to pass, so ASM.js may still be preferable, since it's much closer to actually existing.
- ahomescu1 14y agoI couldn't figure out from the link, how is TAOS different from the JVM/CLR? It seems to me that pNaCl and asm.js are already 99% of that, they're only missing all the libraries.
- stcredzero 14y agoTAOS VM is like pNaCL, in that it's more of a target for implementing a VM than a bytecode compiler target. And yes, ASM.js is already most of this.