What exactly is the "threat" to those players here, wasm?
It baffles me when people are asking for "a mechanism (aka hidden behind-the-scenes magic) for objects and GC" in an assembly language =)
It baffles me when people are asking for "a mechanism (aka hidden behind-the-scenes magic) for objects and GC" in an assembly language =)
(I imagine the threat here is that the more things can be deployed as web apps, the less they depend on any particular desktop OS.)
AFAIK even conservative root-scanning is not possible right now. Please correct me if I am wrong: With the current bytecodes it is only possible to access the heap but not the stack. To make things worse, object references could also be in registers.
1) You can't integrate it with the Javascript GC for interacting with the DOM and other JS-side objects
2) Now you have to distribute the GC with every app that uses it