3 ms·
Might be worth mentioning that Java applets could call into native DLLs (which was a major security risk), while there's no way to do the same from WASM.
by flohofwoe 4y ago
Might be worth mentioning that Java applets could call into native DLLs (which was a major security risk), while there's no way to do the same from WASM.
- mike_hearn 4y agoThey could only call into the JVM runtime, not arbitrary DLLs. WASM can do the same, that's how it talks to the browser. The difference is mostly the kernel sandboxing that browsers do.
- flohofwoe 4y agoNo, you could definitly call into native DLLs from a Java applet. Everything had to be code-signed, and at some point a permission popup was introduced, but it totally worked (that's how I "integrated" a Windows D3D game written in C++ into browsers ca 2010 until Chrome removed Java plugin support).
- mike_hearn 4y agoI stand corrected. I thought the applet SM policy had forbidden JNI completely but forgot that code signing could turn it off.
- whimsicalism 4y agowrong!