Amy is darn good 
-
-
Replying to @hankchizljaw @andybelldesign and
Hard to know where to start...broad statements which may be locally true in a few instances, but are not generally correct. Just a flavour: component styling launched via CSS Shadow Parts (which is, I think, the "custom pseudoclass" point): https://www.chromestatus.com/feature/5763933658939392 …
1 reply 1 retweet 11 likes -
Replying to @slightlylate @andybelldesign and
As for wide support, this is of course a judgement call. But the article is presenting it as a global decision, not one which specific products make based on the totality of interests.
1 reply 0 retweets 3 likes -
Replying to @slightlylate @andybelldesign and
For example, Salesforce has bet the future of their frontend stack on Web Components, even though ~half of their traffic today is still from IE11.
1 reply 4 retweets 13 likes -
Replying to @slightlylate @andybelldesign and
Why do that? Because it gets teams off the "pick a framework, then migrate everything N years later" treadmill. The difference between documenting some polyfill quirks and the fundamental incompatibility of exclusive framework choice is both real and meaningful.
1 reply 4 retweets 18 likes -
Replying to @slightlylate @andybelldesign and
So massive organisations with lots to lose look at the trend, not the moment. This is why YouTube is built on Web Components.
1 reply 1 retweet 7 likes -
Replying to @slightlylate @andybelldesign and
There's a huge library of WCs within Google because they help end the Angular/GWT/Closure/Polymer/whatevs war. Their de-facto compatibility (when built well; not a given) frees teams from an endless series of Sophie's Choice moments regarding features-or-rebasing.
2 replies 2 retweets 5 likes -
Replying to @slightlylate @andybelldesign and
The points about composition and ajax and data sources are basically non-sequitour. They're app-specific choices that don't implicate frontend component system *either way*.
1 reply 0 retweets 3 likes -
Replying to @slightlylate @andybelldesign and
I'm not even going to try to address the "but it won't work without JS" <skip ahead a bit> "here's a JS-driven solution" argument.
2 replies 0 retweets 7 likes -
Well what can I say? I’m glad you overcame the hurdle of not knowing where to start and thank you for sharing your feedback. To clarify, I edited this and I’m not a subject matter expert, but very happy indeed to chat about providing some clear, inclusive counter arguments.
1 reply 0 retweets 1 like
Hey Amy; thanks! In general, I don't think the arguments are _wrong_, but there's a lot more complexity to the space that the title and some of the points seem to admit. What's the best forum to discuss?
-
-
Understood. Why don’t you DM me as a start point and we’ll go from there?
3 replies 0 retweets 2 likes -
Happy to; looks as though your DMs may be closed?
1 reply 0 retweets 0 likes - 1 more reply
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.