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.<p>For what it's worth (excluding client-side issues), I have a high-speed internet connection and a last-gen CPU.<p>Things that are very slow (from 5 to 60 seconds depending on the number of items) for me:<p>- Clicking on "Pull requests" tab for any repo<p>- Opening a PR with many comments (50+)<p>- Opening "Files changed" tab from inside any PR<p>- Marking a file as "viewed" from the "Files changed" tab<p>Tips I found to mitigate this:<p>- Opening the link in a new tab often usually only takes half the time than navigating in your current page.<p>- Review PRs from the visual studio code web ui (github.dev), easily accessible by pressing "." while viewing a PR
GitHub used to be server-side rendered. This is the consequence of drinking the client side framework koolaid.<p>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).
A lot of big websites, e.g. YouTube, Facebook, Reddit, GitHub, have become really bad and sometimes unusable in the past year or two. I think it's mainly due to using unnecessarily complex frontend frameworks and the low quality of code generated by LLMs. It's a vibe.
Possibly related to them just adding stricter rate limits, because AI scrapers won't stop pissing in the pool?<p><a href="https://github.blog/changelog/2025-05-08-updated-rate-limits-for-unauthenticated-requests/" rel="nofollow">https://github.blog/changelog/2025-05-08-updated-rate-limits...</a>
Yes, when navigating a repo's files on an older computer, I noticed that it took an incredible length of time to rehydrate pages or whatever it's doing.