←back to thread

The GitHub website is slow on Safari

(github.com)
446 points talboren | 3 comments | 27 Aug 25 09:43 UTC | HN request time: 0s | source
Show context
PedroBatista ◴[27 Aug 25 13:10 UTC] No.45039192[source]▶
The Github website is slow everywhere. It is truly a piece of shit software both in terms of performance but also UX/UI and everything in between.

It's a product of many cooks and their brilliant ideas and KPIs, a social network for devs and code being the most "brilliant" of them all. For day to day dev operations is something so mediocre even Gitlab looks like the golden standard compared to Github.

And no, the problem is not "Rails" or [ insert any other tech BS to deflect the real problems ].

replies(17): >>45039249 #>>45039365 #>>45039680 #>>45039841 #>>45040328 #>>45040430 #>>45041105 #>>45041125 #>>45041207 #>>45042280 #>>45042385 #>>45044131 #>>45046133 #>>45048521 #>>45050100 #>>45051138 #>>45062005 #
bob1029 ◴[27 Aug 25 13:14 UTC] No.45039249[source]▶
> And no, the problem is not "Rails"

The problem is they abandoned rails for react. The old SSR GitHub experience was very good. You could review massive PRs on any machine before they made the move.

replies(10): >>45039310 #>>45039407 #>>45039686 #>>45040388 #>>45041936 #>>45043631 #>>45048845 #>>45049190 #>>45051019 #>>45051373 #
agos ◴[27 Aug 25 13:29 UTC] No.45039407[source]▶
if you look at the thread, the explanation is not this easy, as much as it's satisfying to blame React (or any other single tech)
replies(5): >>45039679 #>>45039778 #>>45042874 #>>45043242 #>>45051016 #
bob1029 ◴[27 Aug 25 13:52 UTC] No.45039679[source]▶
You're right. The technology is not necessarily flawed. It is more about the people who decided to use it and the way in which they used it.
replies(1): >>45039835 #
agos ◴[27 Aug 25 14:00 UTC] No.45039835[source]▶
exactly. I don't want to do a "no true scotsman" to defend React, but circumstantial evidence suggests that they wildly misused the tool
replies(2): >>45041699 #>>45042753 #
1. throw-the-towel ◴[27 Aug 25 16:20 UTC] No.45041699[source]▶
A tool that lends itself to misuse so easily is a bad tool, period.
replies(2): >>45049805 #>>45051642 #
2. agos ◴[28 Aug 25 08:28 UTC] No.45049805[source]▶
why do you say "easily"? it took them considerable effort to make that atrocity, I'm pretty sure. The fact that tens of people worked on this and yet this is the result is way more telling of the team and company culture than it is of the specific tool.
3. sgarland ◴[28 Aug 25 12:59 UTC] No.45051642[source]▶
Not necessarily. Sharp tools are often sharp because someone needs it.

I’m not a frontend dev, and have next to zero experience with anything beyond jQuery, but an analogy is shell. Bash (and zsh, though I find some of its syntactic sugar nicer, albeit still inscrutable) will happily let you do extremely stupid things, but it also lets you do extremely complicated things in a very concise manner. That doesn’t mean it’s inherently bad, it means you need to know what the hell you’re doing, and use linters, write tests, etc.