Curious what the Web Components thought leaders think of https://github.com/mikeal/shaolin /cc @slightlylate @nolanlawson @jaffathecake
-
-
Replying to @NickColley
: not if they're fast enough by default. Invite you to trace http://shop.polymer-project.org
@mikeal@nolanlawson@jaffathecake@github1 reply 0 retweets 0 likes -
Replying to @slightlylate @NickColley and
: this gets to why "do it all in JS" is a terrible strategy. HTML/CSS parsers can be threaded
1 reply 0 retweets 1 like -
Replying to @slightlylate @NickColley and
: similarly, why HTMLImports are so important: allow chunking of exec, don't block interaction
2 replies 0 retweets 0 likes -
Replying to @slightlylate
interesting, i guess i'd question client thread perf vs server too. TTI could be faster on the client, but what gains after?
1 reply 0 retweets 0 likes -
Replying to @priley86 @slightlylate
most apps are interactive enough to warrant some "churn", so i'll stay isomorphic till' HTML Imp. support improves
1 reply 0 retweets 0 likes -
Replying to @priley86 @slightlylate
fwiw - there just isn't a compelling model for handling state in Polymer yet. complex state happens, it's life.
2 replies 0 retweets 0 likes -
Replying to @priley86 @slightlylate
also - iron-ajax is just another unnecessary element we have to render. CE's render slowly still, even in Chrome.
1 reply 0 retweets 0 likes -
Replying to @priley86 @slightlylate
I find the iron-ajax element quite useful. On my laptop each one costs around 0.002 seconds. ~3x > than div.
2 replies 0 retweets 0 likes
: as always, benchmark end-to-end. Are these common in your app? Is it in critical path? The truth is in the trace.
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.