Ask HN: Did GitHub UI become unbearably slow?
I remember being able to review even large PRs (70-100 files changed) from the web UI fairly easily, but now every time I click a button, the page becomes unresponsive for many seconds.
For what it's worth (excluding client-side issues), I have a high-speed internet connection and a last-gen CPU.
Things that are very slow (from 5 to 60 seconds depending on the number of items) for me:
- Clicking on "Pull requests" tab for any repo
- Opening a PR with many comments (50+)
- Opening "Files changed" tab from inside any PR
- Marking a file as "viewed" from the "Files changed" tab
Tips I found to mitigate this:
- Opening the link in a new tab often usually only takes half the time than navigating in your current page.
- Review PRs from the visual studio code web ui (github.dev), easily accessible by pressing "." while viewing a PR
11 comments
[ 3.1 ms ] story [ 39.8 ms ] threadhttps://github.blog/changelog/2025-05-08-updated-rate-limits...
May be related, or maybe not.
One could argue about how react makes it easier for big orgs to work together or whatever. But, when the whole point of the product is to be a robust productivity tool for developers and they can't do basic tasks without getting frustrated, it doesn't matter. The entire product could become irrelevant if someone exploits this weakness. Speed is a killer feature in a market where few understand how to actually provide it (or have the courage to preserve it).
The only downside is that I now need to juggle between two git servers that don't make mirroring easy. But if (when) Microsoft decides to do something stupid, I at least have an escape hatch.