There's an asymmetry here: I don't post most of what I see to spare folks embarrassment; it's rare that folks want the before/after comparison public. I make exceptions for public sector work as we're all paying for that...but you should know that brokenness is now pervasive.
-
-
Replying to @slightlylate
I guess what I’m saying in this case is that Etsy (for example) has perf problems, but we know it and we’re working hard on it. If this kind of tweet came out about our site, I’d be embarrassed, angry, and hurt. I wouldn’t be _more_ motivated.
2 replies 0 retweets 13 likes -
Replying to @sangster
That's why it's so damned rare that I post these. This was just a wildly egregious example at the end of a long week of egregious examples.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
It seems like you’re saying that this was a bad example, and by calling it out you got a good result — folks are reaching out to get help. What I’m saying is that by going at it this way, you’re fundamentally excluding plenty of people who might otherwise have wanted to as well.
2 replies 0 retweets 2 likes -
Replying to @sangster
I've been at this a long, long time now, and I'm oscillating in approach as a result. I tried to warn everyone; to educate about the networks and devices: https://www.youtube.com/watch?v=4bZvq3nodf4 … ...didn't work...
1 reply 0 retweets 0 likes -
Replying to @slightlylate @sangster
I've tried working (more or less) quietly in the background with dozens and dozens of teams. Often has a good point effect, but can regress and change is only as lasting as management is stable.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @sangster
Have tried to get support for prophylactic, opt-in limits: https://github.com/slightlyoff/never_slow_mode … Not much success there either.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
How is blaming the entire React community a good solution? How does that help you help people? Even you seem to admit that performance regressions after you helped were more about management than developers.
1 reply 0 retweets 0 likes -
Replying to @sangster
The disasters are reliably react (and npm + webpack) affairs and the React community continually venerates the developer (rather than user) experience. You get what you reward.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @sangster
React thought leaders aren't pushing on these issues and FB isn't leading on them (despite persistent pleas). Other communities value speed and the results are different.
2 replies 0 retweets 0 likes
It is *technically* true that React "isn't the problem", but its community is *culturally* culpable. Trickle-down DX doesn't work any better than trickle-down economics did. You have to center the user.
-
-
Replying to @slightlylate @sangster
There are alternatives with very small runtime footprints like Svelte. Why don't you promote those instead? JS is here to stay. There is no point trying to fight that. People won't go back to static PHP style websites from the early 2000s.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.