I don't think those two things are related. But people want to learn one pattern/paradigm for making quality apps instead of 3
-
-
Replying to @jordwalke @slightlylate
For that, you'll need some abstraction layer on top (framework for lack of a better term).
2 replies 0 retweets 1 like -
Replying to @jordwalke
: sure. And we should judge those tools by the apps people produce w/ them. I'm not anti-React, FWIW.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @jordwalke
Started at "time to throw our your frameworks." Don't see how you can say both of these. Either is ok. But both?
1 reply 0 retweets 0 likes -
-
Replying to @slightlylate @asolove
: we can have some nice things, in moderation, but community assumptions abt affordability are *wildly* wrong
1 reply 0 retweets 0 likes -
Replying to @slightlylate @jordwalke
100% agree. Does "throw out your frameworks" help accomplish this? Everyone here agreeing except for that slogan.
1 reply 0 retweets 0 likes -
Replying to @asolove
: helps people understand the overhead/value tradeoff more clearly. Most haven't seen a zero-js page in years.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @asolove
: we can add FWs back in, but only when we start from fast and don't let that regress.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @jordwalke
So your theory is teams hand-rolling js will result in excellent server+client rendering and code splitting?
1 reply 0 retweets 0 likes
: I'm talking about theory of change. Teams starting new work need to reset expectations.
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.