←back to thread

446 points talboren | 2 comments | | HN request time: 0.619s | source
Show context
zackmorris ◴[] 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. CharlesW ◴[] No.45042973[source]
> …on my 2011 Mac Mini which Apple stopped allowing upgrades on past macOS 10.13.

In case you're one of today's lucky 10,000, OpenCore Legacy Patcher supports Macs going to back as far as 2007: https://github.com/dortania/OpenCore-Legacy-Patcher

replies(1): >>45047713 #
2. userbinator ◴[] No.45047713[source]
The newer versions of macOS are also slower than the older ones, so that doesn't solve the actual problem.