GitHub used to be server-side rendered. This is the consequence of drinking the client side framework koolaid.
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).
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.
GitHub used to be server-side rendered. This is the consequence of drinking the client side framework koolaid.
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).
Possibly related to them just adding stricter rate limits, because AI scrapers won't stop pissing in the pool?
https://github.blog/changelog/2025-05-08-updated-rate-limits...
Just to be clear, I am authenticated. Maybe they are struggling with the AI scrapers though, you're right.
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.
Earlier this morning they "temporarily rate banned" me after clicking a total of 3 files in some repository.
May be related, or maybe not.
I like IntelliJ’s Github plugin for reviewing PRs. It’s nice for adding bookmarks and code folding.
Did you add node_modules to your repo by chance?