: BTW, we don't have much evidence that FWs/usage change when platform "arrives".
-
-
Replying to @slightlylate @youyuxi
: to the extent that we do, it's darwinian.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @youyuxi
: e.g., many Google properties are continuing to carry around huge amounts of legacy-compat junk.
1 reply 0 retweets 1 like -
Replying to @slightlylate @youyuxi
: we don't see frameworks making breaking changes to re-architect for new constraints frequently.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @youyuxi
: how many years after rAF was available was jQuery continuing to use crappy setTimeout animations?
1 reply 0 retweets 2 likes -
Replying to @slightlylate @youyuxi
: once a framework finds its audience, the shift in marketing goes from "new capabilities!" to "compat!"
2 replies 0 retweets 2 likes -
Replying to @slightlylate
I can’t speak for other frameworks, but I’m surely thinking constantly about how Vue can adapt to the new constraints
2 replies 0 retweets 7 likes -
Replying to @youyuxi
: the burden becomes architectural. If you define your own API, you need to either break or wrap. Both have costs.
1 reply 0 retweets 1 like -
Replying to @slightlylate
to be fair, Custom Elements are particularly tricky because it’s a new primitive that has overlap with what is conventionally
2 replies 0 retweets 0 likes -
Replying to @youyuxi
: so did rAF, qSA, many array methods, classes, etc.
2 replies 0 retweets 0 likes
: 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 - 34 more replies
New conversation -
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.