It's simpler than that: if I'm starting a new app today, I can either a) hope that my requirements don't evolve to include SVG components, or b) use tools and practices that don't rely on custom elements
-
-
Replying to @Rich_Harris @slightlylate and
You could use today's tech and build your app. And if your needs expand use the tools you need then. Saying you can't use a new tech today because it doesn't solve all future problems is like saying you can't drive the nail because the hammer doesn't work for screws too!
1 reply 0 retweets 2 likes -
Replying to @BenDelarre @Rich_Harris and
This is ludicrous. Start with WC and if you end up needing svg support rebuild it all?
1 reply 0 retweets 6 likes -
Replying to @evilpingwin @BenDelarre and
yeah, that's borderline professional negligence. you need to pick technologies that won't paint you into a corner
1 reply 0 retweets 5 likes -
Replying to @Rich_Harris @evilpingwin and
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!
3 replies 0 retweets 2 likes -
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
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.
-
-
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 - 33 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.