: this is literally what "pave the cowpath" gets you; a situation where libraries appear bloated *in retrospect*.
-
-
Replying to @slightlylate
: an analogy: for a few years after CSS got rounded corners, Google properties were sending tables w/ bg images for rounding.
2 replies 0 retweets 1 like -
Replying to @slightlylate
not sure if that’s a particularly relevant one…
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: now we either had duplication in code or had to shift out something that was used pervasively.
1 reply 0 retweets 0 likes -
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
: and that's becoming *critical* as the web goes mobile. Most FWs are not appropriate; some have made the turn.
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.