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 …
-
-
It's simpler than that: if I'm starting a new app today, I can either a) hope that my requirements don't evolve to include SVG components, or b) use tools and practices that don't rely on custom elements
-
You could use today's tech and build your app. And if your needs expand use the tools you need then. Saying you can't use a new tech today because it doesn't solve all future problems is like saying you can't drive the nail because the hammer doesn't work for screws too!
- 44 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.