Specifically, @briankardell captures how the evolutionary process that the Extensible Web (and Web Components) creates needs JS to function
-
-
Replying to @slightlylate
...yet the goal is to need less of it over time by giving browsers confidence to follow where the community has lead.
2 replies 2 retweets 7 likes -
Replying to @slightlylate
And the reality us that, today, most of the historic anti-script arguments have become irrelevant. Search engines run script, e.g.
3 replies 2 retweets 6 likes -
Replying to @slightlylate
And notions of a11y not interacting well with script are, at best, outdated
3 replies 2 retweets 10 likes -
Replying to @slightlylate
At the same time, most script on the web today provides negative value to users.
2 replies 5 retweets 11 likes -
Replying to @slightlylate
This is why I talk about *user outcomes*, not "script vs. no script". We need to be able to talk about bad user experiences w/o religion
2 replies 6 retweets 19 likes -
Replying to @slightlylate
My I/O talk is largely about this: https://youtu.be/a5X_Ot-R6lo Yes, you can always go faster w/o script, but you can't evolve w/o it
3 replies 6 retweets 16 likes -
Replying to @slightlylate
So we need to learn to talk about "fast vs slow" and "usable vs unusable" w/o fetishizing edge cases (which, btw, a11y isn't)
1 reply 2 retweets 3 likes -
Replying to @slightlylate
So to the library/framework authors I say this: if you haven't seen what Polymer dropped at I/O (PRPL), you missed the future.
1 reply 4 retweets 10 likes -
Replying to @slightlylate
It's the only pattern I've seen that gets script in play without negative value creation, precisely because it uses the platform to evolve
1 reply 2 retweets 4 likes
/end tweetstorm because takeoff
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.