So, web components • break a11y • break progressive enhancement (no SSR, broken without JS) • don't work with SVG • share a global namespace instead of being modular • ... Imagine how much tedious moralising we'd see if JS frameworks shipped with similar limitationshttps://twitter.com/sarahmei/status/1198069119897047041 …
-
-
I don’t think it’s misbegotten, I think you’re focusing on correctness and I’m trying to express intuitiveness. The idea that a JS API (that has no non-JS fallback) will help remove our dependence from JS is understandably counter-intuitive.
-
I further think that it is not unreasonable to predict that having such a fundamental part of basic web UI rely on JS (in a way nothing before has had to), *might* inadvertently signal a green light to use *more* JS.
- 3 more replies
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.