51–54 of 54 posts
Earlier quoted context omitted.
I think there is a difference between "compile once, run everywhere" and "code once, compile (for) everywhere".
Well, one the developers are smart enough to create optimized packages for each architecture but instead if they wanted to cater to bad practice JS fans they could create a universal binary.
Earlier quoted context omitted.
Well, one the developers are smart enough to create optimized packages for each architecture but instead if they wanted to cater to bad practice JS fans they could create a universal binary.
Yeah sandbox security and isolated runtimes are horrible and all.
Earlier quoted context omitted.
Wrong? There isn’t a right or wrong about this. It is often the job of vulnerability assessment team to get down to the root of the misbehaving components, WASM or not.
Yes there is. Fixing WASM for anything but VM holes is like changing your CPU because your Login screen accepts "password" as valid for every user name.
Earlier quoted context omitted.
Yeah sandbox security and isolated runtimes are horrible and all.
Those already exist without WASM