First, let me be *ultra* clear that I'm about to talk about AMP-the-collection-of-web-components, not AMP-the-experience-in-search.
-
-
Replying to @slightlylate @seldo
That said, I started (and for several years helped lead) the team that built Web Components because my view is that standards have *failed*
2 replies 0 retweets 0 likes -
Replying to @slightlylate @seldo
...when it comes to the vocabulary of HTML, specifically. Standards stopped keeping pace in '99-'01 and didn't catch back up.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @seldo
The quality of existing designs was...low; see e.g.
@notwaldorf's various expositions on form controls.1 reply 0 retweets 2 likes -
In general, standards have been built here through delayed simulated annealing. The use-cases were discovered too late, by too few people
1 reply 0 retweets 1 like -
And so my general take on Standards and their role is that Standards are what come *last* in a long process. The start is design & iteration
1 reply 0 retweets 3 likes -
If you do design inside formal standards process, you destroy the ability to iterate. Standards (narrowly) are about documents, not design
1 reply 0 retweets 6 likes -
So to make good standards, we need more inputs, more explorations, more reports from the field & more research. More design + iterate.
1 reply 0 retweets 4 likes -
One of the worst parts of the JS ecosystem is that it walls itself off from markup. It tries to act as though it's "above" or disconnected
2 replies 1 retweet 4 likes -
Replying to @slightlylate
Alex don’t wanna show your roll here, but can you convince new twitter to not reply to me anymore, please? :/
1 reply 0 retweets 1 like
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.