...and no, this doesn't mean that Web Components are all-singing, all-dancing. Some fidelity with current practice *will* be lost. That's OK
-
-
Replying to @slightlylate
...and it's OK for same reason it was OK to not get 100% fidelity with everything you could w/ <table> + <img> to build rounded corners
1 reply 0 retweets 2 likes -
Replying to @slightlylate
...the difference in weight & ecosystem-wide compatibility are overwhelmingly positive. They outweigh local benefits of alternatives.
1 reply 0 retweets 3 likes -
Replying to @slightlylate
^^^, BTW, is why it was also a good idea to push Promises into the language (despite the massive personal costs to
@domenic and myself).2 replies 0 retweets 3 likes -
Replying to @slightlylate
Global benefits are just that: hard to see from your particular patch. But they are also real and they do matter.
1 reply 2 retweets 4 likes -
Replying to @slightlylate
So, in a world where the world's most popular computers have flaky network connections and slow CPUs, anything that sheds JS is _golden_.
3 replies 8 retweets 18 likes -
Replying to @slightlylate
If your framework of choice isn't moving to Web Components for the leaf nodes, it's carrying too much weight in 2016.
3 replies 15 retweets 24 likes -
Replying to @slightlylate
Frameworks without a path to Web Components are the 2016 equivalent of systems that still use <table> + <img> for rounded corners.
4 replies 22 retweets 40 likes -
Replying to @slightlylate
.
@slightlylate this is exactly the problem I have with Web Components: instead of designed to complement existing FWs, it is designed with3 replies 1 retweet 11 likes -
Replying to @youyuxi
: huh? You can use each of the pieces independently, and it absolutely interoperates. If your FW genereates DOM, it can use WC.
2 replies 0 retweets 2 likes
: it's literally the most interoperable thing you can do. You put <your-element> in the DOM, browser inflates it.
-
-
Replying to @slightlylate
: then you just treat it like all other DOM elements w/ properties & attributes.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: like, maybe you FW only renders to canvas? If so, you'll need some adapter logic..but otherwise...
0 replies 0 retweets 0 likes
End of conversation
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.