3 ms·
Ask HN: What do you think about GitHub's Gradual Degredation?
In recent years, GitHub has become increasingly hostile towards users who choose to not run JavaScript by default on their browser.
Basic features went from fully functional to broken. From the activity log to displaying commit information in file listings. They
all worked in the past, and at some point became dependent on JavaScript with no recourse.
I had to make do with these lapses in quality, always hoping for a reversal, but GitHub poor design values persist. Come their latest
manifestation: the menu you got when you clicked on the little avatar icon on the top right of the page is now replaced by a useless "Sorry, something went wrong." message.
This blow hits hard and therefore I feel the need to write about this long-standing issue. It also troubles me that few people, presumably none working for GitHub, seem to care about it. Since the issue is likely to exacerbate, I am considering further action.
- scrollaway 6y ago> Since the issue is likely to exacerbate, I am considering further action. Like what, enabling Javascript? Frankly, it sounds like you'd be better served by a service such as sircmpwn's Sourcehut (https://sr.ht/ https://sr.ht/).
- bluefox 6y agoNo, I will not enable JavaScript. There's no need to respond with snark. You're telling me I can stop using GitHub: I know that already. I am bringing this issue here to have a chance at avoiding that. Re-hosting my repositories is one thing. The other is that I would like to interact with other people's repositories, which happen to be on GitHub.
- auslegung 6y agoIt would be nice if more websites were usable without JavaScript, but our only hope is to fight very hard for very long
- bluefox 6y agoThe tragic thing is that GitHub was usable that way from the start, and for some reason seemingly adopted a policy of deterioration.