With every major browser supporting WC or about to, frameworks not supporting them are making a choice *against* interop and *for* lockin at this very late date: https://custom-elements-everywhere.com/ https://twitter.com/ElliottZ/status/1134790076599193600 …
-
-
Not really. If you make a fancy angular elements combo box and it emits a web component, you still include the angular runtime which is quite large. If you include a stencil, a preact, a lit, etc custom el, the runtimes do add up. Lit HTML is insanely awesome. I want it built in!
-
...and with Ivy it'll get tiny. And if you so this with any of Lit, Preact, Svelte, or Stencil it *already is*. We need to stop excusing the legacy desktop frameworks for dragging their legacy into 2019.
- 3 more replies
New conversation -
-
-
After reading this tweet I'm not mad at react, but I realise I should really stop using that excuse for smoking when I drink.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
. Can we give the frameworks a minute? I think support became ubiquitous like a week ago. If it’s still a situation in two years, then sure, but right now tools need to come up with a path where they don’t break their users.