It became difficult as Web technologies grown complexier, such as implementing native CPU instructions through WASM, bluetooth through Web Bluetooth, 3D graphics through WebGL, NFC, motion sensors, serial ports, and so on. Nowadays, it's simply too hard to maintain a browser engine, because many of the former alternatives were abandoned and became deprecated.

[–] zea_64@lemmy.blahaj.zone 9 points 2 months ago (1 children)

I dare anyone to even just compile a document containing all the standards you'd need to implement

[–] dsilverz@thelemmy.club 17 points 2 months ago

Actually, there is a compilation of all the standards specifications. It's on W3 (World Wide Web Consortium), where all the technical details are deeply documented (called "Technical Reports"), available on https://www.w3.org/TR/ . To this day, there are 309 published Technical Reports regarding "Standard" specifications.

Fun fact: while seeking for the link to send here, I came across a Candidate Standard entitled "Web Neural Network API", published exactly yesterday. Seems like they're intending to implement browser-native neural network capabilities inside Web specifications, and seems like the "closer future" I mentioned is even closer... 🤔

[–] superb@lemmy.blahaj.zone 1 points 2 months ago* (last edited 2 months ago)

implementing native CPU instructions through WASM

This is purely a nitpick, but WASM lets you run WASM instructions not native cpu instructions. Its does let you get much closer to the speed of running native instructions