4 ms·
It's not even conceptual. It's an entirely separate, kludgy and vastly inelegant, reinvention of a concept that had already been done much better. First in Ta
by lproven 3y ago
It's not even conceptual.
It's an entirely separate, kludgy and vastly inelegant, reinvention of a concept that had already been done much better.
First in Tao Group's Taos, later much refined and improved in Elate and Intent.
Then done in a more Unixy way in Inferno.
Inferno embeds the cross-platform runtime VM right into the kernel and makes it the default.
WASM bodges a cross-platform runtime VM together out of chunks of web browser and Javascript tech, and then others rip it out of the browser and make it run standalone.
- garaetjjte 3y agoThere is basically none Javascript tech in WASM.
- lproven 3y agoAs I understand it, and I could be wrong, the origins of the project lay in trying to target the output from a compiler to a bytecode like intermediate language that the JavaScript runtime could execute. I am more than happy to believe that no trace of that is left now, but I think that is more or less how it got started.