Post #2752806

2026-05-14 18:21 UTC

So TL:DR, chrome is like internet explorer was before firefox. It does some things outside the standard, and because it’s the modern day “default”. sites sloppily code to work with it, and other browsers are left carrying the bag because if tiktok doesn’t work on firefox, people will view that as a firefox problem. Even if firefox is the one actually following the standards when tiktok and chrome aren’t.

Replies (8)

@pycorax@sh.itjust.works 2026-05-15 03:44

Same issue with AMD’s drivers sometimes. Not to say that their drivers are perfect but as a graphics engineer, I’ve had stuff my colleagues wrote and tested on Nvidia work fine but break on AMD because AMD was implementing the OpenGL spec exactly but Nvidia decided to be “lenient” and add hacks that make incomplete code work.

Open ##2752805
@jimmy90@lemmy.world 2026-05-15 06:55

deeeep tech analysis from lemmings as usual actually no. IE dominated because MS owned the desktop and still do. IE was fucking awful and did not care about standards chrome dominated because it was fucking great. chrome now defines standards because the other browsers lag behind and standards themselves lag behind if anything safari is the new IE in apples fucking awful walled garden

Open ##2760142
@einkorn@feddit.org 2026-05-14 18:41

I think similar how the EU adopted the USB-C as mandatory standard for charging, it should force other industries, including software vendors, to follow commonly defined standards. In case of browsers that is Chrome using it’s de facto monopoly to force other browser to rush to catch up with their custom crap. Yes, as a side effect that would also break a lot of existing webpages because they rely heavily on browser bending over backwards to accommodate sites serving effectively broken HTML i.e. but in the long term this would improve the internet as a whole.

Open ##2765865
@A_norny_mousse@piefed.zip 2026-05-14 18:51

Thanks you saved me a click. Google has been doing this with all kinds of (web) standards, and the industry has always obeyed. Fuck'em all.

Open ##3010177
@kureta@lemmy.ml 2026-05-14 21:28

Shit like this will continue to happen until governments start enforcing interoperable open standards and resume enforcing antitrust laws, which were, in practice, suspended for a long time, for whatever reason.

Open ##3010178
@ImgurRefugee114@reddthat.com 2026-05-16 05:15

Reminds me of how much effort GPU driver devs put in to fixing completely borked games that don't follow spec / violate apis / rely on undocumented or undefined behaviour / etc It's a really dumb situation...

Open ##3010179
@SkaveRat@discuss.tchncs.de 2026-05-14 18:53

as a webdev: this is (mostly) not really chrome's fault. It's the fault of devs not testing or not getting enough time to get something run on more than just chrome. For too long the web standards were "eh, it's stable enough. works on one browser, works on all". But that only holds true for the basic feature set. When you start using features that are not super common, the browser implementations start to diverge slightly. And that needs to be tested for. But often isn't

Open ##3010180
@MonkderVierte@lemmy.zip 2026-05-14 18:45

Actually, it's somewhere about 160 standards and around 120 are expected and the rest are 50:50 mostly supported or optional. And each browser has a different set of the 50:50. But yeah, lock-in effect still applies. Btw, a few years back last i looked, but QtWebKit supported most standards of all engines.

Open ##3010181