←back to thread

The GitHub website is slow on Safari

(github.com)
446 points talboren | 8 comments | 27 Aug 25 09:43 UTC | HN request time: 0.001s | source | bottom
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 #
dylan604 ◴[27 Aug 25 15:13 UTC] No.45040845[source]▶
> on my 2011 Mac Mini which Apple stopped allowing upgrades on past macOS 10.13

I know some people feel like Apple is aggressive in this respect, but that's an 8 year old version of a browser. That's like taking off all of the locks on your house, leaving the doors and windows open all while expecting your house to never have uninvited guests.

replies(2): >>45041210 #>>45042447 #
1. makeitdouble ◴[27 Aug 25 15:41 UTC] No.45041210[source]▶
But Apple is also the one locking Safari to the OS, IE style. Having to buy a new machine to get the latest and secure version of a browser is a pretty heavy requirement.
replies(2): >>45041500 #>>45041503 #
2. sipjca ◴[27 Aug 25 16:04 UTC] No.45041500[source]▶
i mean there are also lots of browser options to be fair.

should they be locking safari to the OS, definitely not. but users can just go download another browser if they are actually concerned.

replies(1): >>45042649 #
3. w0m ◴[27 Aug 25 16:04 UTC] No.45041503[source]▶
or use a supported OS (linux, or hilariously probably Windows), or install a still-suppored browser (I'd guess Firefox likely still runs latest on there).

I'd put it on the end user for not updating software on 15 y/o hardware and still expecting the outside world to interact cleanly.

replies(1): >>45041925 #
4. makeitdouble ◴[27 Aug 25 16:39 UTC] No.45041925[source]▶
> hilariously probably Windows

That's probably true.

> 15 y/0

It's a matter of expectations, many laptops that old still work decently enough with a refreshed battery. Funnily enough win10 was released 15 ago, and one can still get support for it for at least another 3 years until 2028, even on the customer license.

replies(1): >>45042977 #
5. dylan604 ◴[27 Aug 25 17:43 UTC] No.45042649[source]▶
Will modern versions of those other browsers still work on an 8 year old OS, or has it been updated where it is no longer compatible? So much effort has been put into hardware rendering, and the mechanisms for the browser to interact with that hardware has changed within those OS versions. Forcing the user to download an older compatible version of the browser to work with the older OS is also tossing away potential security fixes.
replies(1): >>45048529 #
6. Autummata ◴[27 Aug 25 18:08 UTC] No.45042977{3}[source]▶
W10 was released 10 years ago, not 15. https://en.wikipedia.org/wiki/Windows_10_version_history
replies(1): >>45045993 #
7. makeitdouble ◴[27 Aug 25 22:13 UTC] No.45045993{4}[source]▶
Sorry, I just have pattern matched the 2015 release year instead of properly counting.
8. sipjca ◴[28 Aug 25 04:55 UTC] No.45048529{3}[source]▶
i mean you're also throwing away security fixed running an OS that out of date, but the person doing this probably doesn't care about security anyway.