←back to thread

446 points talboren | 1 comments | | HN request time: 0.202s | 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 #
dylan604 ◴[] 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 #
forgotmypw17 ◴[] No.45042447[source]
> 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.

Depending on where you live (or what websites you visit) it's not unreasonable.

replies(1): >>45044048 #
dwaite ◴[] No.45044048[source]
Attacks via ad networks mean that is likely limited more than people would expect.
replies(1): >>45080653 #
1. forgotmypw17 ◴[] No.45080653[source]
That's a good point. I assumed they use an effective ad blocker.