11–20 of 346 posts
Ok, now we need GC and DOM interop. Because reinventing layouts is pain.
In order to port other languages (Haskell, Go, Python) to target WASM, we definitely need the possibility of writing a GC in WASM. But to build an efficient GC, we need multithreading and synchronization/memory barrier primitives.
Java applets 2.0, we are back to square one, yet again. People don't learn. The web dev community have just managed to force browsermakers to unify web development on browser side JS, and throw Java applets, activex, and action script to the bucket, just to have a kind of JVM being made a part of the web standard, and forced upon us yet again.
Ok, now we need GC and DOM interop. Because reinventing layouts is pain.
In order to port other languages (Haskell, Go, Python) to target WASM, we definitely need the possibility of writing a GC in WASM. But to build an efficient GC, we need multithreading and synchronization/memory barrier primitives.
Java applets 2.0, we are back to square one, yet again. People don't learn. The web dev community have just managed to force browsermakers to unify web development on browser side JS, and throw Java applets, activex, and action script to the bucket, just to have a kind of JVM being made a part of the web standard, and forced upon us yet again.
Java applets 2.0, we are back to square one, yet again. People don't learn. The web dev community have just managed to force browsermakers to unify web development on browser side JS, and throw Java applets, activex, and action script to the bucket, just to have a kind of JVM being made a part of the web standard, and forced upon us yet again.
Earlier quoted context omitted.
In order to port other languages (Haskell, Go, Python) to target WASM, we definitely need the possibility of writing a GC in WASM. But to build an efficient GC, we need multithreading and synchronization/memory barrier primitives.
Seems to be on the roadmap: http://webassembly.org/docs/future-features/
Can't wait for DOM interop and get away from JS on frontend. Seriously JS should not be the lingua franca of the web :)
But neither should this. Really, keep your code off my computer as much as possible.
Ok, now we need GC and DOM interop. Because reinventing layouts is pain.
IIRC you can do GC within WebAssembly (though it's less nice and awkward as I've been told). But DOM interop is needed. Can't wait to get my fingers on the DOM via native C code :)
[0]: https://github.com/WebAssembly/design/issues/1079
edit: Scratch all of that above. I stand corrected. Here's the DOM proposal: https://github.com/WebAssembly/host-bindings/
Can't wait for DOM interop and get away from JS on frontend. Seriously JS should not be the lingua franca of the web :)
>> Seriously JS should not be the lingua franca of the web But neither should this. Really, keep your code off my computer as much as possible.
I can't imagine there are many people in this world who have a computer with more than even 1% their own code running on it.