Re:WebContainers: Run Node.js natively in the browser
by kevingadd on Thursday May 20, 2021 @03:57PM
(#27226325)
Typically when you see stuff like this be Chromium-only, it's because Chromium has a bunch of non-standard/one-vendor-only stuff enabled in production builds and neither Firefox or Safari have it enabled (or implemented at all). A few examples include Bluetooth, MIDI and USB.
[ Parent
| on HN ]
Re:WebContainers: Run Node.js natively in the browser
by pantelisk on Thursday May 20, 2021 @04:36PM
(#27226859)
I don't understand why you are downvoted. Filesystem access is another big one! Chrome has the technological advantage and sports an enormous kitchen sink of features. One has to make the hard decision, work on a concept that will work only on one browser, try to cut corners with graceful (or crippling) degradation, or wait potentially a long time until a spec is standardized and implemented. The latter may result in others hitting the market sooner, so it is understandable why we end up with web-apps that function in a single browser only. Hopefully this improves in the future.
Re:WebContainers: Run Node.js natively in the browser
by mr_toad on Thursday May 20, 2021 @10:26PM
(#27229864)
The down side is that some of these technologies never get standardised and eventually get dropped. Like NaCl and PNaCl.
Re:WebContainers: Run Node.js natively in the browser
by WorldMaker on Friday May 21, 2021 @03:11PM
(#27238561)
Or for an example that caused a lot more havoc comparatively: WebSQL.