If you’re developing web sites that only run in Google Chrome, you are not a web developer, you’re a web destroyer.
#google #chrome #WebIntegrityAPI #WebDRM #web #dev #SiliconValley #adtech #PeopleFarming #SurveillanceCapitalism
If you’re developing web sites that only run in Google Chrome, you are not a web developer, you’re a web destroyer. #google #chrome #WebIntegrityAPI #WebDRM #web #dev #SiliconValley #adtech #PeopleFarming #SurveillanceCapitalism 10 comments
@aral I quite *liked* the IE4 document.all[] model. It felt elegant to me, and it was much easier to do dHTML in IE. However, the businesses paying me to build their shit wanted to reach *everyone*, and that was higher priority than sparkly UI. And they were right. @aral I would also add: if your educational blog needs JavaScript enabled to dismiss the (non-compliant) GDPR fullscreen "banner" with a huge "Accept all" button, a small "Manage preferences" with lots of "legitimate interests" and no "Reject all" banner then you are telling me to ban your website on my Pihole. The blog probably doesn't even look at their tracking data. So they're annoying their users for nothing. @aral I didn't even know this was possible, I always use Firefox myself. People who do this are maybe the same who use DIVs instead of semantic elements, type="text" on every input field etc. Sigh. I'm having Old-guy flashbacks to IE specific code and Netscape Navigator.... *shudders* |
@aral we had this debate in the late 90s when Netscape 4 and IE4 implemented differing DOMs.
Ultimately, the w3c standard won out, but the browser wars, as intense as they were, were even less polarised than now. I do worry about this.