Brian's latest gets to why I shrug when people ask about how things should work without JavaScript enabled:https://briankardell.wordpress.com/2016/06/02/x-web-days-of-future-past/ …
-
-
Replying to @slightlylate
Specifically,
@briankardell captures how the evolutionary process that the Extensible Web (and Web Components) creates needs JS to function1 reply 4 retweets 7 likes -
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
@slightlylate 100x this! It's not script that's bad It's how we prioritize things extremely poorly It's about ethics in JS prioritization1 reply 0 retweets 4 likes -
Replying to @nzgb @slightlylate
Also, we must do better at delivering customizable native controls. World's largest runtime but no way to style <select> input
1 reply 0 retweets 4 likes -
Replying to @nzgb
: yes. Web Components were the first attempt. Slow going. Most browser vendors had to be taught how bad their product is/was.
1 reply 0 retweets 1 like
: with CE/SD/Templates/ES6 builtin-extension + classes, we can think about that now
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.