Published a quick piece on my recent WebComponet adventures.https://www.patreon.com/posts/14535714
-
-
Replying to @mikeal
How's perf? I'm skeptical that instantiating a shitload of Web Components will be faster than rendering a shitload of React components.
4 replies 0 retweets 1 like -
Replying to @tomdale
I'm much more interested in the ease of distribution. Being able to get back to a simple <script> include is pretty amazing.
2 replies 1 retweet 3 likes -
Replying to @mikeal
But what about when everyone is doing this and you have 100s or 1000s of them on a page?
4 replies 0 retweets 1 like -
Good thing that we have build systems that can take care of the transport optimization independently of your authoring abstraction
1 reply 0 retweets 0 likes -
Note original tweet said instantiating, not loading.
1 reply 0 retweets 0 likes -
Sadly, the synchronous-vs.-async instantiation question went the wrong way Because Apple (TM), but many options to handle this well.
1 reply 0 retweets 1 like -
Replying to @slightlylate @tomdale and
In my experience WCs don't significantly impact best practices around advisable DOM node count. Too many = unhappiness.
1 reply 0 retweets 1 like
Also, impls are actively driving down instantiation time. It's a big focus for our DOM team.
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.