the point is, WC as is currently specced does not deliver what it claims to solve, and FWs see little value in
-
-
Replying to @youyuxi
: it's cool. Hopefully your framework can achieve reasonable perf some other way (although I worry). /cc
@aerotwist2 replies 0 retweets 0 likes -
Replying to @slightlylate @aerotwist
I don’t see where the perf point is.
1 reply 0 retweets 0 likes -
Replying to @youyuxi
: 2 related things. First go look at this: https://www.youtube.com/watch?v=J4i0xJnQUzU …
1 reply 0 retweets 6 likes -
Replying to @slightlylate @youyuxi
: what I'm seeing is that the build/module/runtime systems of frameworks cause far too much code to be included up-front
2 replies 0 retweets 2 likes -
Replying to @slightlylate @youyuxi
: I covered this here: https://www.youtube.com/watch?v=a5X_Ot-R6lo …
1 reply 0 retweets 6 likes -
Replying to @slightlylate @youyuxi
: baaaaascially current build/module/load systems & framework integrations don't load granularly enough, nor cache enough
1 reply 0 retweets 2 likes -
Replying to @slightlylate @youyuxi
: the interplay of these things takes a long time to tease out; most frameworks don't own all parts. Farming bits out.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @youyuxi
: but when I sit down to trace, e.g., a frameworky app these days, I know what I'm gonna see most times...
1 reply 0 retweets 0 likes -
Replying to @slightlylate @youyuxi
: maybe some "server-rendered" early UI, but almost always a big bundle of script that pegs mobile CPU for seconds
3 replies 0 retweets 2 likes
: and because of the way that stuff loads, you can't interact w/ it. Basically hung. Not interactive.
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.