: now we either had duplication in code or had to shift out something that was used pervasively.
-
-
Replying to @slightlylate
: in retrospect, the decision looks easy. More browsers every year that support rounded corners.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: but change in architecture allowed code removal + node removal. Nearly linear speedup.
2 replies 0 retweets 0 likes -
Replying to @slightlylate
well I’m not denying that FWs today can potentially cause friction in adoption of new primitives
1 reply 0 retweets 1 like -
Replying to @youyuxi @slightlylate
but 1. that’s not the intention of FW authors; 2. FWs are still a net improvement vs. old platform sans new primitives
1 reply 0 retweets 0 likes -
Replying to @youyuxi
: right. What I'm getting at is that frameworks can create "overhang". Major un-banked opportunities to go faster.
2 replies 0 retweets 0 likes -
Replying to @slightlylate
that is true, but the overly negative narratives against FWs feel like placing all the blames on FW authors
1 reply 0 retweets 1 like -
Replying to @youyuxi
: FW authors are in a privileged position. Default FW choices become the most-common outcomes for apps that adopt them.
2 replies 0 retweets 0 likes -
Replying to @slightlylate
but on the other hand FW authors also can play the critical role in accelerating adoption of new primitives, if done right
1 reply 0 retweets 1 like -
Replying to @youyuxi
: ...which is exactly why frameworks like Polymer exist. To show what's possible and help accelerate adoption.
2 replies 0 retweets 1 like
: so, now, that's the new bar. Being good enough on mobile, not pegging scarce cores, building in offline-first architecture.
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.