3 ms·
Well, the JVM was supposed to be this, but turned out to be too closely tied to the Java language, as well as too heavyweight for a lot of webpages (getting rep
by ummonk 8y ago
Well, the JVM was supposed to be this, but turned out to be too closely tied to the Java language, as well as too heavyweight for a lot of webpages (getting replaced by HTML5 instead). It's interesting to see us coming full circle with WebAssembly, albeit with a much more language neutral, multi-vendor framework.
- kettlecorn 8y agoI was going to bring up the JVM because it definitely was an attempt at the same goal. I think the obstacles this time around will be very similar for WASM, but it stands a far better chance due to its language and vendor neutrality, as you mentioned. For user facing applications there remains the question of what sort of cross platform UI framework could accompany WASM. Or should WASM just remain coupled to the Web? Java’s UI solutions were often received very poorly and led to Java’s bad reputation amongst consumer software. Analyzing the desires and goals of the big players (Google, Microsoft, Apple) with regards to how Wasm might develop is interesting.
- kodablah 8y ago> Well, the JVM was supposed to be this, but turned out to be too closely tied to the Java language, as well as too heavyweight for a lot of webpages Agreed, but want to add wrt tied to Java the language, that stdlib it carries around is a large burden too. WASM will need a stdlib one day or suffer portability, so here's to hoping whichever one is adopted is small and simple (no, posix is not good enough like emscripten and this lib work with).
- thrower123 8y agoAs we've seen with JS, an anemic standard library is also a big problem. Hopefully npm-isms dont infect WebAssembly, but I don't hold out much hope.
- krapp 8y agoWhy does WebAssembly need its own standard library? No one is going to be writing code directly in it, any more than they would write Java bytecode by hand.
- kodablah 8y agoI can't even write a function accepting a string because there is no notion of string. Every piece of WASM written carries the runtime of the source language making sharing code much more difficult and bloating binaries with duplicate logic. It doesn't need one stdlib as part of the WASM project, but sooner or later people are going to want to share, e.g. a socket. Even without a full blown stdlib, known data types need to be shared beyond just the structs that are coming with the GC proposal.
- krapp 8y agoThat's fair, even C has chars and char arrays. I don't know about strings, since every language has its own idea of what a string is. Even something as simple as an "array" has different behaviors between different languages... some languages only have maps that also act like arrays, some index from 1 rather than 0. If Webassembly wants to remain as agnostic as possible, I don't think there's much more complexity they could add.
- thrower123 8y agoBeing agnostic is a good goal, but being useful is more important. Hopefully they get it right, because the JS ecosystem is a bloated mess that we've been stuck with because there's no other game in town.
- raxxorrax 8y agoI believe we would miss it dearly if wasm gains significant traction. I wouldn't like running closed binaries with monolithic architectures through my browser. Maybe for a few selected high performance applications. Not because the security aspect but I think it will be detrimental to an open web. Maybe not, we'll see. edit: I don't really understand people that are not horrified by the thought of replacing general javascript code with one that is written in c/c++... Because string operations are awesome in these languages, right?!
- mooman219 8y agoThe JVM as a kernel module would be interesting I'm not sure where the hate for this comment is coming from though given the submission is also talking about adding a runtime into kernel space.
- pjmlp 8y agoSun did actually implement a Solaris kernel JVM. "Writing Solaris Device Drivers in Java" http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.92.1892&rep=rep1&type=pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.92....