Chrome impliments the necessary features for wasm and webgl. Here's a test: checkaux.github.io
Mobile firefox lacks simd, i haven't been able to get its shared memory to work on a local or deployed environment because of bugs in what it thinks is a 'secure context'
Desktop and mobile Firefox does not support OffscreenCanvas without turning on flags. It's been years since this was meant to be made. Therefore you cannot use seperate threads to render to webgl without using less performant workarounds.
Lack of proper threading means bad page performance.
There's lots more dumb bugs and features firefox said it would support and simply never did. Understand there's real reasons as to why chrome is the preferred. it works and it actually puts in the necessary features.
Then there is no point in having a browser platform, because we are back where we started from.
Then why don’t we simply run JVM apps, there are at least a handful of implementations, and it has at least a decent GUI (half joking here).
But really, the JVM is where WASM may be several years later.
VM's are not all the same, and a VM does not at all guarantee security.
The JVM is not designed to run arbitrary code and/or is not as well designed to do it as Javascript or Wasm is.
If it were as simple as plug JVM into browser it would be done. However it's not, because the memory and execution safety measures are better in Javascript and Wasm.
Wasm should actually have better isolation than JS.
If you want to know the details go read the spec and look at the implimentations.
Java Applets were a security risk, but it was decades ago. Modern JVM has many options to sandbox a running app.
But it seems that WASM tries to be a mininal CPU target instead, which is questionable - I can’t wait seeing memory errors (even if only inside a single webpage) on the web. With the good quality GCs available with JS, but even more so on JVM, I would say that running system languages should not be the point.
Mobile firefox lacks simd, i haven't been able to get its shared memory to work on a local or deployed environment because of bugs in what it thinks is a 'secure context'
Desktop and mobile Firefox does not support OffscreenCanvas without turning on flags. It's been years since this was meant to be made. Therefore you cannot use seperate threads to render to webgl without using less performant workarounds.
Lack of proper threading means bad page performance.
There's lots more dumb bugs and features firefox said it would support and simply never did. Understand there's real reasons as to why chrome is the preferred. it works and it actually puts in the necessary features.