It seems like I need to be more explicit part 3 in -- specifically for webdevs -- in my blog post series about standards (a small thread): https://infrequently.org/2018/06/effective-standards-work-part-1-the-lay-of-the-land/ … https://infrequently.org/2018/06/effective-standards-work-part-2-threading-the-needle/ …
-
-
By then the damage was done, and couldn't be undone without breaking tons of existing sites. And so we're *still* dealing with the repercussions 20 years on. This is where the blowback comes from. Call it an overreaction, maybe, but it's not without cause.
-
Nobody is fetishizing standards for their own sake. It's just honest concern that another powerful company with > 80% market share risks repeating the mistakes of the last one. It's great that Google wants to push the web forward. But some critical pushback is also healthy.
- 9 more replies
New conversation -
-
-
Can confirm, I remember this the same way and been in many similar arguments since. IE6 was a good browser at the time it won the browser wars and IMO the most reliably standards compliant. People scoff, I suppose because the the years after understandably overwrite that.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.