The Extensible Web Manifesto didn’t fail. Instead we discovered it makes some people feel the web is being forked when a set of extensions get enough traction that they start to influence the underlying platform. Thus we need a definition of success that more people can accept.https://twitter.com/matthewcp/status/1201573824564736002 …
-
-
Replying to @ade_oshineye
The second part of the manifesto, where high-level APIs came as a result of incubation of the low-level ones, never happened. And as a result of only having low-level features devs were forced to throw more JS at their apps, to dire consequences.
3 replies 0 retweets 1 like -
Replying to @matthewcp
It’s been happening but nobody has aggregated them somewhere so people can see it. I’m sure that
@cramforce and@pbakaus can probably tell you how many high-level platform features were inspired by AMP functionality. /cc@slightlylate for the bigger picture.1 reply 0 retweets 1 like
A few examples of bottom-up working inside the platform (not AMP related per sae): - async/await layered on top of Promises semantics - Animation Worklet/Scroll Timeline integrating with Web Animations - Some work happening now in new form controls happening as a result of libs
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.