Is there a good write up of this problem? I don’t understand why it would require re-parsing; Twitter doesn’t seem like the right medium for an explainer.
-
-
It's probably buried in a comment on a random GitHub issue. Cause that's how we roll.
1 reply 0 retweets 6 likes -
This is I think one of the biggest problems in web standards. There’s all of this stuff that “everybody knows” but there’s nothing you can link to explaining it. It’s in a slide deck. It’s in a github comment that means nothing out of context. It’s in an earlier draft of a spec.
5 replies 1 retweet 0 likes -
Without disagreeing that we should be constantly seeking to improve the standards process and make it more inclusive, can we appreciate for a moment what an improvement it is that today these things *can* be found on a slide deck or in a GitHub comment?
3 replies 0 retweets 19 likes -
So much of this stuff used to happen entirely behind closed doors, and that only improved because of the enormous effort of people who believed strongly in the need to open the process up to the world.
2 replies 0 retweets 5 likes -
The limiting factor IMO is time and energy. People already feel like standards bodies move too slowly. Gaining consensus across so many different groups is emotionally exhausting, and that’s before dealing with the general public. It’s a hard balance to get right.
2 replies 0 retweets 6 likes -
I've advocated over the years that
@w3c and others should have individual membership classes whose dues pay into a more democratically-allocated budget for travel and representation. Glad JS Foundation is doing more of this now, but not the same.1 reply 1 retweet 6 likes -
Replying to @slightlylate @tomdale and
The crisis of legitimacy is why I've forced our teams to use incubation (modeled on IETF and Raf's TC39 process, which we now take for granted). Going to places where you can more easily meet users *matters* at the early stages.
2 replies 0 retweets 1 like -
Replying to @slightlylate @tomdale and
Most SDOs aren't comfortable with discussing funding models and believe they have an evergreen model and constituency. It ain't so.
@w3c, e.g., is currently suffering for not building a broader coalition (after many, many warnings).1 reply 0 retweets 0 likes -
Replying to @slightlylate @tomdale and
At the same time, the web (overall) isn't succeeding on mobile. The data I see is more dire than it's ever been. Nobody will go to the web for anything in ~5 years. When it's a pervasively bad time, why would you? Standards are downstream of use.
3 replies 1 retweet 5 likes
In summary: iPhone-user-apologists have evaporated our window of opportunity. The mobile web is most likely to be a footnote in the transition to non-browser super-apps.
-
-
-
Replying to @slightlylate @tomdale and
The impact on SDOs of the platforms they front for becoming irrelevant will be gradual, then calamitous. The survival of the low-overhead forums will be cold comfort.
0 replies 0 retweets 0 likes
End of conversation
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.