- reimplement browser features and do a bad job of it
- are unnecessarily slow
- try to stop being slow by breaking even more stuff
Some examples I’ve come across within the last week:
- Twitter pages randomly failing to load until the next hard refresh, probably because of service workers somehow (which are unnecessary for user experience improvement since HTTP cache exists and I don’t have notifications enabled)
- Twitter’s offscreen tweets not being searchable with browser find because they were optimized out of existence – and I want to do this in the first place because it decided to refresh itself while I was in the middle of reading
- YouTube application state getting out of sync with browser history that it overrides when I navigate Back too fast for it – the URL stops matching what’s playing and the navigation doesn’t take place
- GitHub’s reimplementation of browser navigation reimplementing a loading indicator but not the stop button (I think I’ve also gotten it out of sync before)
- Form state not being restorable across history navigation because the fields didn’t exist when the page loaded
- Reddit’s redesign is so unusably sluggish that I don’t stay on it long enough to run into any other problems
> Reddit’s redesign is so unusably sluggish that I don’t stay on it long enough to run into any other problems
I agree with everything you said, but allow me to reiterate this point. Reddit's redesign is the most hostile thing I've ever seen. It explicitly blocks me from reading the discussion. What's the point, then? It's absolutely unusable. If they ever remove old.reddit.com, I'm not following a Reddit link ever again.
I started reading your list looking for something to argue with but I'm sadly agreeing with all your points which I encountered myself.
I didn't even realize they're reimplementing browser features and that's a really cool observation.
I think it's paramount to understand that this is not a list of bugs to fix, it's a list to convince us that we should consider Server Side Rendering more often and avoid client side navigation, history API with all its possible race conditions...
- reimplement browser features and do a bad job of it
- are unnecessarily slow
- try to stop being slow by breaking even more stuff
Some examples I’ve come across within the last week:
- Twitter pages randomly failing to load until the next hard refresh, probably because of service workers somehow (which are unnecessary for user experience improvement since HTTP cache exists and I don’t have notifications enabled)
- Twitter’s offscreen tweets not being searchable with browser find because they were optimized out of existence – and I want to do this in the first place because it decided to refresh itself while I was in the middle of reading
- YouTube application state getting out of sync with browser history that it overrides when I navigate Back too fast for it – the URL stops matching what’s playing and the navigation doesn’t take place
- GitHub’s reimplementation of browser navigation reimplementing a loading indicator but not the stop button (I think I’ve also gotten it out of sync before)
- Form state not being restorable across history navigation because the fields didn’t exist when the page loaded
- Reddit’s redesign is so unusably sluggish that I don’t stay on it long enough to run into any other problems