←back to thread

The GitHub website is slow on Safari

(github.com)
446 points talboren | 1 comments | 27 Aug 25 09:43 UTC | HN request time: 0.214s | source
Show context
zackmorris ◴[27 Aug 25 13:56 UTC] No.45039765[source]▶
GitHub moved to a JavaScript rendering mode almost as soon as Microsoft bought it. Previously, I had been able to browse it with JavaScript disabled on my 2011 Mac Mini which Apple stopped allowing upgrades on past macOS 10.13. So even if I enable JavaScript, I can no longer browse GitHub, because they didn't bother to make their build compatible with browser versions as old as mine.

It's hard to know which member of the duopoly is more guilty for breaking GitHub for me, but I find that blaming both often guarantees success.

I could like, buy a new computer and stuff. But you know, the whole Turing complete thing feels like a lie in the age of planned obsolescence. So web standards are too.

replies(6): >>45040146 #>>45040845 #>>45040924 #>>45042018 #>>45042973 #>>45064741 #
1. sipjca ◴[27 Aug 25 14:23 UTC] No.45040146[source]▶
How does Turing completeness feel like a lie?

Planned obsolescence is some of it, some of it is abstractions making it easier for more people to make software (at the cost of using significantly more compute) and Moore’s law being able to support those abstraction layers. Just imagine if every piece of software had to be written in C, the world would look a whole lot different.

I also think we’ve gone a bit too far into abstraction land, but hey, that’s where we are and it’s unlikely we are going back.

Turing completeness is almost an unrelated concept in all of this if you ask me, and if anything it’s because of completeness that has driven higher and higher memory and compute requirements.