Live data from Hacker News

Why is GitHub UI getting slower?

yoyo-code.com

81–90 of 123 posts

Re: Why is GitHub UI getting slower?

#82
Interestingly enough, the iOS app has been working really well for me.

Performance, usability and overall adaptability to the phone size, it is incredible how a native app can be that good.

I wish the Web UI performed as well as the native iOS app.

Re: Why is GitHub UI getting slower?

#84
post #55

I'm building a new Git hosting service, focused on performance and using HTMX. For example, compare page load time: - https://gitpatch.com/gitpatch/git-demo - https://github.com/git/git

How does this compare to codeberg?

Codeberg UI appears to be pretty similar to GitHub, so it's great as GitHub alternative. It's powered by Forgejo, fork of Gitea.

Gitpatch is a bit different. It implements a new storage backend and Git library from scratch. It also uses patch-based model for code review vs pull requests, where specially-named branches are used to submit patches and patch stacks.

Re: Why is GitHub UI getting slower?

#85

I suffer it and that’s why I’m building https://githero.app Btw, I worked at GitHub for 3 years and they are very aware that slowness is a big issue throughout the whole product. There was a year long cross team effort to improve things but the main goals were not achieved IMO and it shows.

This looks pretty cool! Do you have a privacy policy?

Thanks!

Good question. I don't have now right now but I can prepare one soon. In any case I store zero information from users. When you are logged in traffic goes directly from your browser to GitHub.

Re: Why is GitHub UI getting slower?

#86
post #54
post #4

Githubs performance has been rapidly degrading ever since they started rewriting everything in React. It's basically impossible to view diffs now because they often fail to load, render correctly, or just are incredibly slow.

I was baffled by the technical blog post they published on this subject, in 2023: https://github.blog/engineering/architecture-optimization/cr... They completely redesigned the code navigation to load it dynamically using React. One of the regressions introduced caused the entries to be duplicated when searching for a word using Ctrl+F. Their solution to address this issue? Decompose the source character by character…

Trying to find a string in github actions logs is just impossible. Not to mention that even opening large logs takes many seconds of animated scrolling to get to the end.

There is the "view raw logs" button which just opens a plaintext file that my browser loads and searches instantly (imagine that), but doesn't work for still-running jobs.

Re: Why is GitHub UI getting slower?

#87

Earlier quoted context omitted.

After all years of advancement in computing, and in the year 2025 it's not possible to show a 5000 lines diff anymore.

I just mean that if you are reviewing over 5k lines of code, it suggests your PR is too big and should have been broken up into smaller changes.

It's not always code. I sometimes review things like translations that are often done in bulk (thousands of strings in a single batch). There's not much structure to it, it's not like reviewing some weird multi threaded super complicated algorithm, you just need to skim it quickly and make sure that the structure is not broken, and there are no screaming text blocks or unnecessary profanities.

Anyway, it did work properly, now it doesn't. The response shouldn't be "you're holding it wrong".

Re: Why is GitHub UI getting slower?

#89

Earlier quoted context omitted.

After all years of advancement in computing, and in the year 2025 it's not possible to show a 5000 lines diff anymore.

I just mean that if you are reviewing over 5k lines of code, it suggests your PR is too big and should have been broken up into smaller changes.

I'm not always reviewing code. Sometimes I'm checking a diff between two versions of the code, which might contain multiple commits.
Post reply on HN