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
-
-
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 @jkup and
Are they tho? ;)pic.twitter.com/2g9L2fuaGb
1 reply 0 retweets 2 likes -
Replying to @AdamRackis @jkup and
On https://custom-elements-everywhere.com/ ? Yes?
2 replies 0 retweets 3 likes -
Replying to @slightlylate @jkup and
@sebmarkbage page doesn't specify version of React used - you happen to know if v16 w/ the many dom changes improves this at all?1 reply 0 retweets 0 likes -
Replying to @AdamRackis @slightlylate and
Active discussion in https://github.com/facebook/react/issues/11347 … There isn't a clear WC community standard approach yet. No stable checkboxes.
2 replies 0 retweets 3 likes -
Replying to @sebmarkbage @AdamRackis and
Btw, it seems easier to me for these frameworks to talk directly to each other with a simple JS layer than through WC. Impedance mismatch.
2 replies 0 retweets 3 likes
is "simple JS layer" === "setting properties"? If so, DOM supports that. Just do it.
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.