4 ms·
... We've really reinvented the JVM. Not sure that's bad; hope we can do better this time.
by yjftsjthsd-h 7y ago
... We've really reinvented the JVM. Not sure that's bad; hope we can do better this time.
- sanxiyn 7y agoWhen is ETA of JVM value type again? WebAssembly already got it.
- pjmlp 7y agoAs does the CLR, TIMI, PNaCL, Apple's bitcode variant of LLVM. And the long forgotten SWF, P-Code, M-Code, UNCOL, ANDF, Xerox bytecode.
- deleted 7y ago[deleted]
- monocasa 7y agoNo gc.
- xena 7y agoPractically this is a blessing and a curse. I really wish there was a better story for GC'd apps on WebAssembly because a GC is super expensive at the moment.
- jameskilton 7y agoI like to think of it more that Javascript/WebASM will finally accomplish what Java spent decades trying to do: be the completely ubiquitous hardware-independent code platform. Javascript has truly become the "Write Once, Run Anywhere" language. https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript https://www.destroyallsoftware.com/talks/the-birth-and-death... (2014)
- bsagdiyev 7y agoPlease, no.
- xena 7y agoBad news, that talk has been a constant source of inspiration for my entire endeavors :)
- bsagdiyev 7y agoThat's fine, I'll continue to disagree and understand that we'll never work together since we move fast and don't break things where I work.
- dang 7y ago"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something." https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- Negitivefrags 7y agoSpectre came along and ruined the awesome conclusion of that talk. The idea was that the cost of using WASM would be entirely offset by the speedup of removing the cost of hardware memory protection. We could do that if everything ran in one big VM because the VM would enforce the memory protection. Unfortunately, now we can't rely on a VM for memory protection anymore. We have to assume that any code running in the same address space can access any memory in the same address space. So we need the hardware memory protection after all. You can say goodbye to your WASM-only future.
- colordrops 7y agoI assume that new chips will address this vulnerability, correct? Couldn't the VM detect whether the hardware is secure and decide whether to use hardware memory protection or not?
- _bxg1 7y agoOne important difference is that GC isn't baked in, so in a way Wasm is actually lower-level than the JVM.
- snek 7y agoAn optional GC is being added: https://github.com/WebAssembly/gc/blob/master/proposals/gc/Overview.md https://github.com/WebAssembly/gc/blob/master/proposals/gc/O... (Emphasis on optional)
- _bxg1 7y agoYep, so that way you have the option of one or the other
- deleted 7y ago[deleted]
- jimmcslim 7y agoWould it be reasonable to see a WebAssembly VM that is implemented in silicon? Perhaps on an FPGA as a first step?
- _bxg1 7y agoNo idea, although it might defeat the purpose a bit (which doesn't mean nobody would do it)
- accurrent 7y agoIt would be hard because traditionally most of our hardware relies on the register memory model. Implementing a hardware stack can be done but there are very few silicon CPUs like that thus a lot of the research which has been done on getting register machines up to speed in terms of caching and speculation could be difficult. Then there is the fact that webassembly doesn't use branch labels rather it uses blocks, which AFAIK have never actually been used on traditional CPU hardware. People have tried to create high level language CPUs but often failed in terms of performance. An overview can be found here: https://en.wikipedia.org/wiki/High-level_language_computer_architecture https://en.wikipedia.org/wiki/High-level_language_computer_a...