as I said, should focus more on the problems themselves rather than implying the problems are caused by frameworks
-
-
-
Replying to @youyuxi
But as a dev I *can* fix it when I use Custom Elements, but I *can’t* fix it if the code is locked up in a library / framework.
2 replies 0 retweets 3 likes -
-
Replying to @youyuxi
I can do that with Vanilla, too. It's more a question of Inversion of Control.
1 reply 0 retweets 1 like -
Replying to @aerotwist
yes you can, but consider the efficiency and maintaining cost when you hand roll everything w/ vanilla.
1 reply 0 retweets 3 likes -
Replying to @youyuxi
I do, which is why I don’t want people to stop using frameworks, I want us collectively to get better.
1 reply 0 retweets 5 likes -
Replying to @aerotwist
that's great to hear. Also this thread is not specifically targeting you, but Chrome devrel in general.
1 reply 0 retweets 0 likes -
Replying to @youyuxi
: BTW, we don't have much evidence that FWs/usage change when platform "arrives".
1 reply 1 retweet 1 like -
Replying to @slightlylate @youyuxi
: to the extent that we do, it's darwinian.
1 reply 0 retweets 0 likes
: e.g., many Google properties are continuing to carry around huge amounts of legacy-compat junk.
-
-
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 - 42 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.