3 ms·
Not until hardware became fast enough and compilers performant enough to support this, and not until everyone had to learn their lessons with approaches like th
by phoe-krk 4y ago
Not until hardware became fast enough and compilers performant enough to support this, and not until everyone had to learn their lessons with approaches like the JVM.
- amelius 4y ago> Not until hardware became fast enough and compilers performant enough to support this Yes, but the easy part is to think about what would be possible if hardware was fast enough. Not sure what you mean by lessons learned from JVM.
- phoe-krk 4y agoI meant that automatic garbage collection is not always the way to go for some people, especially in the days when JVM GCs were not as advanced as they are now.
- amelius 4y agoOk. Yes, ideally you'd allow the user of your VM to implement their own GC. But to make this fast you typically need to support special memory barrier instructions, like a modern CPU does. Anyway, the GC-included approach is of course the one taken by Javascript and JVM.
- phoe-krk 4y agoI assume that's one of the parts of the work done at https://github.com/WebAssembly/gc https://github.com/WebAssembly/gc - not happening any soon yet, but it'll eventually be done.
- pjmlp 4y agoI doubt it will ever be happening, everyone will keep shipping the runtimes on their WASM blobs and that will be it. Instead of adopting PNaCL in 2011, here we are a decade later still trying to figure out how WASM will be able to support all computing models.
- pjmlp 4y agoSystem 360, Burroughs B5000, Xerox Alto, Xerox Star, Xerox Daedilon, AS/400, Lilith, Ceres,... Such a couple of examples of platforms using bytecodes as main executable format.