5 ms·
I'm not going to waste my time repeating myself on everybody who disagrees with my usage of the word "accessible", since I already explained in another comment
by DreamScatter 6y ago
I'm not going to waste my time repeating myself on everybody who disagrees with my usage of the word "accessible", since I already explained in another comment why it's not accessible. The word accessible is certainly appropriate.
- ebg13 6y ago> I already explained in another comment why it's not accessible You've explained why you don't like it, not why it's any less accessible by the definition that you're choosing to use.
- DreamScatter 6y agoWhat is it with this dictionary language policing? How about you actually discuss the topic instead of trying to make this an issue about dictionary definitions. You seem to be smart enough to realize that I'm not referring to disability accessibility, so why don't you focus on the actual topic instead of definitions? Tell me why the new design is better when I can't see the repository languages without additional input and mental effort, if you want to contribute to the discussion.
- deleted 6y ago[deleted]
- darekkay 6y ago"Accessibility" has a special meaning in design/development. It's as you've said "The new GitHub website is less performant" because you cannot access the data as fast as before. It's confusing, and that's why you're facing "dictionary language policing". From "web accessibility" perspective (which does not only focus on disabilities), none of your points are "valid". From UX perspective, it may be a totally different thing. You answer(s) were rather condemning, hence noone seems to be willing to participate with you in a constructive debate. But let me give a try: - "languages are not at the top anymore" - I almost never look for the project languages. If I'm opening a specific project, I usually already know what language it is using. If I'm searching for a project, I will use a filter. For me, the change is perfectly fine. - "stars and tabs off-centered" - I agree, it looks strange. Not a huge thing for me, though. As with _any_ redesign, there will _always_ be an initial pushback. But I personally mostly like the new redesign.
- ebg13 6y ago> "Accessibility" has a special meaning in design/development Side note: The meaning doesn't change because we talk about a different space. Access is access is access. If we ever apply the word differently, it's just because we're focusing on different aspects of access. But that's not what's happening here. What's happening here is that OP is whining about things they don't like while pretending that their taste has anything to do with _any_ definition of accessibility and then getting defensive about it. Like you, I also think that de-prioritizing the languages was a positive change. And yet it's OP's very first complaint under the guise of losing access. Like they'd been wronged or something. Calling the new design "awful", "awkward", and "less accessible" over really petty marginal shit like stars, followers, and languages without recognizing what was gained as a result (latest release!) or the subjectivity of taste feels like a real "I demand to speak to your manager!" moment.
- DreamScatter 6y agoWell, I'm tempted to setup my own self hosted git repository now, because I really don't like the way it looks and how the information is organized. Having the latest release on the side is not really a gain, it should be at the top center, not on the side bar. I really prefer the way it was before with a bar having the license and releases and so on. They could have just added the release number there instead of making a terrible layout.