I really wish the conversion about web components was better framed.
Web components will NOT replace your framework.
They are awesome because they don't NEED to replace your framework to provide massive value to you.
-
-
You call them "leaf component rewrites." For React in particular, I guess you mean that this would not follow the recommendation here, to wrap existing React components in custom elements?https://reactjs.org/docs/web-components.html …
-
Or maybe you mean the process works like this? 1) Wrap leaf nodes as WCs 2) Port leaf clients to WC API 3) Rewrite leaf nodes to stop using framework 4) New projects reconsider framework 5) Framework disappears?
- 17 more replies
New conversation -
-
-
Exactly. But unfortunately this doesn't have a good headline.

-
In our drupalcon talk about webcomponents in CMS space I tell a story about accessibility and correcting errors at scale in 15 minutes that used to derail my day
End of conversation
New conversation -
-
-
Also FWs get slimer and slimer and become DSLs that compile down to WC (I'm looking at you svelte 3 :) )
-
I wish that were true. Unfortunately compiling to WCs introduces overhead relative to plain JavaScript classes
- 27 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.
to highlighting cases where web components allow folks to swap out a large fw for something lighter and more interoperable, but provocative headlines & context-free statements hurt more than help, IMO.