3 ms·
This ignores the tons and tons and tons of work that would really have changed that. I don't think it really has anything to do with whether you have one true l
by DannyBee 8y ago
This ignores the tons and tons and tons of work that would really have changed that.
I don't think it really has anything to do with whether you have one true language or not.
There were plenty of well-funded efforts to have "write once, run everywhere" in the past that were just VM's and formats (ANDF, etc).
In practice, a lot of things have changed since Java that have made this kind of approach feasible. As a simple example: good compiler infrastructure to build on top of is much more available than it was then. These days you pretty much just have to write a frontend.
Even though GCC existed then, it was still compiling statement at a time!
- drzaiusx11 8y agoI know there have been many efforts to write a universal VM. Two things I think will make wasm more successful than prior attempts is: 1. it comes on with platforms already via a browser or node.js 2. like you said, the tools are here now (really LLVM made most of this possible)
- DannyBee 8y agoSure, i'm just saying your comment seemed to be saying "java's write-once run everywhere failing was due to trying to have one true language", and i think that part is fairly orthogonal.
- drzaiusx11 8y agoI don't believe it's failure is entirely based on it shipping with a prescribed language--but I wouldn't say it's orthogonal. Java, the language, promised "write once, run everywhere" whereas the JVM in the beginning was just an implementation detail. The JVM slowly evolved into a universal vm concept, mostly at the hands of the community and not those (Sun, Oracle) that had the most control over it.