Miss the point much? WC do not lock you in at all. Because they are HTML and standards based anything that works with HTML works with WC. Use WCs where it makes sense. When you need more use the appropriate tool. It'll interop with WC because it has to if it supports HTML!
-
-
Replying to @BenDelarre @evilpingwin and
Rich Harris Retweeted Rich Harris
If you don't think that supporting this use case is important, or don't understand why WCs fail at it, then I don't think we're going to see eye to eye.https://twitter.com/Rich_Harris/status/1198339672361119745 …
Rich Harris added,
1 reply 0 retweets 4 likes -
Replying to @Rich_Harris @BenDelarre and
Do React or Angular or VueJS support this?
1 reply 0 retweets 1 like -
-
Replying to @Rich_Harris @BenDelarre and
Could you point to any example? I am failing to google anything like this.
3 replies 0 retweets 0 likes -
Replying to @dmitryshimkin @BenDelarre and
Here, I just made this for you: https://codesandbox.io/s/priceless-archimedes-4pxxp …. You can do the same thing in basically any non-WC framework, but it's completely impossible with web components
2 replies 0 retweets 5 likes -
Replying to @Rich_Harris @dmitryshimkin and
Agree that SVG not being extensible yet is not great! Proprietary, non-interoperable parallel-tree systems have an advantage until it is. How big that advantage is depends on need to vend SVG sub-elements, ofc.
1 reply 0 retweets 4 likes -
Replying to @slightlylate @dmitryshimkin and
As someone who does what I do for a living, I can tell you that it's absolutely essential. Most WC advocacy appears to be around BigCorp Design System Enterprise Edition, so it's easy to see why this critical use case (met by UI frameworks since at least 2013) was overlooked
2 replies 0 retweets 8 likes -
Replying to @Rich_Harris @dmitryshimkin and
I don't know who you're arguing against at this point, but the caricature vs. the effort involved in making progress on these issues is doubly exhausting. LMK when you want to put an oar in to help fix.
1 reply 0 retweets 4 likes -
Replying to @slightlylate @dmitryshimkin and
What's exhausting is the suggestion that only those directly contributing to these standards have the right to point out their flaws. If I put an oar in, I'm going to be rowing in a different direction to you, because I think the boat is pointing the wrong way!
1 reply 0 retweets 12 likes
You're attributing malign or ignorant motivation -- that we didn't look at SVG extensibility (we did; went for HTML first) -- to a situation far more complex than your characterisation. If you spent this effort lobbying Mozilla and Apple for this, it could get done quickly.
-
-
Replying to @slightlylate @Rich_Harris and
WC feature dev slowed after '16 as we waited for Mozilla and MSFT to catch up. Took their sweet, sweet time. Big new proposals moving faster recently, landing apace: intrinsic role, form participation, :part, etc. SVG (and MathML) extensibility need attention now.
1 reply 0 retweets 3 likes -
Replying to @slightlylate @dmitryshimkin and
I'm attributing nothing of the sort — I know perfectly well that everyone here is smart and has good intent, and have never — would never — imply otherwise. But here you are again implying it's somehow my responsibility to convince Apple and Mozilla to prioritise these things,
2 replies 0 retweets 7 likes - 29 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.