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/ …
-
-
I don’t think KPIs for browser vendors should include # of new APIs shipped, which seems to be how the chrome team operates. Shipping a bunch of half baked APIs that no other vendor will ever ship is irresponsible and not good for the web.
-
This is deep in Not Even Wrong territory. Happy to discuss in a less agro forum. My DMs are open.
End of conversation
New conversation -
-
-
Does that work for Apple? They rarely share their decision making process at all in public channels. Like, for example,https://github.com/w3c/manifest/issues/835 …
-
It’s possible that rniwa was basing this decision on something, but most everybody in the thread struggled to identify what. Maybe it was/is evidence based, or maybe it wasn’t, but without going behind the scenes at Apple, I feel like I just can’t know what they’re thinking.
- 2 more replies
New conversation -
-
-
Firefox’s shipping of subgrid being an excellent example of such leadership.https://adactio.com/notes/16344
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
couldn’t agree more.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.