this post was submitted on 31 Aug 2024
877 points (98.6% liked)
196
16233 readers
1753 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Then Alphabet will come up with a new bullshit idea, "remove the limits for 'trusted' advertisers" so that they can inject more code than allowed as long as they keep paying for their ad "partnership"
That's why we need to fight against chromium monopoly
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.
I dare anyone to even just compile a document containing all the standards you'd need to implement
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... 🤔
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
Exactly.. Including themselves, as they are a major player in advertising market (Google Adsense).