Earlier quoted context omitted.
There's a standard for most things happening in a browser There's POSIX, too. In practice, divergences are plentiful. Differences among current browsers are more among performance and experimental features The fact that are huge web tables meticulously documenting feature compatibilities across browsers implies differently. Besides, a lot of web standards are done post-facto. I don't see the situation as being any be…
> There's POSIX POSIX + a standard library for UI components + containerization + webassembly would be the "correct", cleanroom solution in my opinion. If you want to build and run "native but untrusted" applications on the user's computer on heterogenous environments and can't anticipate which APIs someone is going to need next. Well then give them access to a walled-off part of the computer. Same-origin policy? Rep…
(Related fact: While Windows is still as bad in that it gets its own things wrong, at least they weren't tied to POSIX's filesystem layout)