PSA: embedding/applying CSS in JS is the surefire way to be on every slow path. Bloats memory, slows parsing & use, hurts caching. Avoid.
-
-
Replying to @slightlylate
we should be fixing these perf problems instead of trying to shame developers out of a preferred workflow.
6 replies 3 retweets 32 likes -
Replying to @mikeal @slightlylate
‘Preferred workflow’ is the problem. If your preference is ergonomics over UX then you’re already wrong, surely?
2 replies 0 retweets 5 likes -
Replying to @csswizardry @slightlylate
depends, if the bottleneck is physical network then yes, but if it's current browser implementation perf then no.
4 replies 0 retweets 0 likes -
Replying to @mikeal @slightlylate
Browsers already go above and beyond what they ought to to remedy lazy developers IMO, but there are still people […]
1 reply 0 retweets 2 likes -
Replying to @csswizardry @slightlylate
meh, perf is a moving target on every platform, including the web.
2 replies 0 retweets 0 likes -
Replying to @mikeal @slightlylate
Exactly. And developers moving away from well documented good/best practices is not sensible. Can’t just shrug and […]
3 replies 0 retweets 0 likes -
Replying to @csswizardry @slightlylate
we're not going back to a time where people are using less JavaScript to build their apps. /end
1 reply 0 retweets 2 likes -
Replying to @mikeal
: ok, then you're objecting to arguments I didn't make. Cool.
1 reply 0 retweets 1 like -
Replying to @slightlylate @csswizardry
I think we're way past whatever the initial comments were. I hardly remember them.
1 reply 0 retweets 0 likes
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.


