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/ …
-
-
But what <toast> highlighted, more than anything, was how standards processes are abused by folks looking to distract from their own lack of proposals and leadership. Nobody mounting high horses abt <toast> was volunteering resources to research counter-proposals, IIRC.
-
If Google implements something that developers can use outside of an official standards process, whether it's "officially released" or not is irrelevant. Chrome feels a lot like the new IE6 in terms of "we just do what we want"
- 12 more replies
New conversation -
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.