Wait I get confused here. WCs are a primitive. Frameworks could (hypothetically) all generate and consume them right? They don't provide 1/
-
-
Replying to @jkup @ken_wheeler and
state management. The ideal world would be all JS frameworks generate WCs but that can't really work bc react/vue depend on vdom 2/2
2 replies 0 retweets 0 likes -
Replying to @jkup @ken_wheeler and
Right - QED. No state management out of the box - need an abstraction like Skate.
1 reply 0 retweets 1 like -
Replying to @AdamRackis @ken_wheeler and
I'm just saying they aren't a framework replacement, they are a primitive. The issue is that they are a primitive all frameworks can't use
3 replies 0 retweets 5 likes -
Replying to @jkup @AdamRackis and
Any framework that knows how to drive DOM can consume them. See:https://custom-elements-everywhere.com/
2 replies 0 retweets 4 likes -
Replying to @slightlylate @AdamRackis and
Right. The *real* problem to solve IMO is how to converge VDOM with WCs. Because react/vue are very popular!
2 replies 0 retweets 0 likes -
Replying to @jkup @AdamRackis and
That's already "solved". You can easily drive your WC internally and externally using VDOM if you like.
1 reply 0 retweets 1 like
The important thing here is to assume that the component is a boundary of behavior.
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.