5 ms·
Unfortunately WASM on iOS could only be interpreted, not JITed, due to protected memory. Also WASM works in Mobile Safari and SFSafariViewController, but not i
by nickmain 7y ago
Unfortunately WASM on iOS could only be interpreted, not JITed, due to protected memory.
Also WASM works in Mobile Safari and SFSafariViewController, but not in WKWebView - which limits its interaction with an app.
- GreaterFool 7y agoWasm is great for sandboxing so iOS could make Wasm first-class native citizen. Then Wasm module could have access to anything and everything iOS and one could write "native" iOS applications using any language that compiles to Wasm.
- manwe150 7y agoIs it though (a good sandbox, I mean)? A modern OS already tries very hard to be a sandbox that can run anything. What does Wasm bring to the table for iOS? I also feel like this is just a weird year for software, because we've got Wasm making huge strides ("let's make it easy to sandbox everything like javascript"), discovered Spectre ("oops, our assumptions about javascript being a good sandbox were maybe wrong, we apparently need to use hardware-enforced process separation"), but also many other permutations of these things in other spaces (such as the WSL2 announcement of a new integrated Windows-Linux environment, vs. containers vs. VMs vs. WSL1 vs. Wine vs. micro-services).