: 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
: but we didn't expect the linear speedup in element count reduction.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: wasn't easy to reason about. But it turns out that when you change the architecture to use platform more, often big gains.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: ...but those gains aren't universal (growing, not there yet) and they aren't obvious (browsers contain multitudes!)
1 reply 0 retweets 0 likes
: here's a fun one: did you know that Shadow DOM's get their own style resolver that's faster?
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.