←back to thread

The GitHub website is slow on Safari

(github.com)
446 points talboren | 9 comments | 27 Aug 25 09:43 UTC | HN request time: 0.417s | source | bottom
1. futurecat ◴[27 Aug 25 13:07 UTC] No.45039143[source]▶
GitHub Actions is such a pain to use just because of how sluggish it feels. I hope they’ll improve performance.
replies(3): >>45039419 #>>45039523 #>>45048887 #
2. Roark66 ◴[27 Aug 25 13:30 UTC] No.45039419[source]▶
We used to use bitbucket Web hooks that used to trigger Jenkins jobs. This was almost instant. Now after migrating to GH actions it can take minutes before jobs start on push for example...
replies(1): >>45039585 #
3. blibble ◴[27 Aug 25 13:39 UTC] No.45039523[source]▶
> I hope they’ll improve performance.

it's Microsoft, so the answer is: buy a new computer

(which comes with a bundled Windows license)

replies(2): >>45039554 #>>45039625 #
4. futurecat ◴[27 Aug 25 13:41 UTC] No.45039554[source]▶
yeah I'll keep my M3
5. simooooo ◴[27 Aug 25 13:44 UTC] No.45039585[source]▶
How big are these jobs? I’ve never seen an action take more than 15s to start
6. layer8 ◴[27 Aug 25 13:47 UTC] No.45039625[source]▶
We are at a point where buying a new computer doesn’t actually help.
7. wheybags ◴[28 Aug 25 05:53 UTC] No.45048887[source]▶
It also continuously fails to scroll down in the log view when watching output of a ci job live, and has done for years. It's so annoying that I made a userscript to force scrolling: https://github.com/wheybags/userscripts/blob/main/github_act...
replies(1): >>45049830 #
8. futurecat ◴[28 Aug 25 08:31 UTC] No.45049830[source]▶
I feel you. The UX is a gigantic mess. Navigating between jobs and builds is also a terrible experience.
replies(1): >>45050361 #
9. wheybags ◴[28 Aug 25 10:05 UTC] No.45050361{3}[source]▶
Oh man. Start a manual job, wait for it to appear in the UI. 10 minutes later, it finally appears. Or just refresh the page manually immediately after starting the job, and there it is...