@Elizafox NaCL was a transparent attempt at ActiveX Part 2 - WebAssembly isn't that much better...

> And Google is unilaterally dictating standards by abusing its market position

so much this - Google is ramming through standards to cause fatigue implementing them for people who aren't google, and for shit that is a security hazard waiting to happen and only good for ChromeOS (cough WebUSB)

@Elizafox well, true in that WebASM has buy in - I just hate it on a moral level

@Elizafox more "the web is a document platform, you bastards!"

but that fight was lost decades ago, so I'll just continue to be bitter on the web

@Elizafox @calvin The problem is that every attempt to use WWW as an application platform has basically been guaranteed to be horrible.

ActiveX: Horrible, insecure, and proprietary.
Java: Horrible, insecure, slow, and conflicting compatibility.
Shockwave: Horrible, slow.
Flash: Horrible, insecure, slow.
JavaScript+HTML5: Horrible, horrifically slow.
Silverlight: Horrible, proprietary.
NaCl: Ditto.
WebAssembly: Probably horrible and insecure.

@calvin @Elizafox

π—–π—›π—”π—‘π—šπ—˜ 𝗠𝗬 π— π—œπ—‘π——

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!