I wouldn't say the GitHub UI sucks.

I wouldn't say the GitHub UI sucks. All you need to do is look back to SourceForge—even before they completely sold their soul to the devil—to understand that GitHub was actually a huge step forward in the UI department. They do a lot right: powerful features, snappy file browser, very good discussion view in Pull Requests, etc. Granted, there are a lot of warts and confusing navigation and organization, but in many ways this is a function of trying to serve so many disparate use cases. Certainly it could be a lot better, but it's far from easy—certainly not the type of thing you could just throw a UX designer at, but something where you need a UX visionary who also happens to be a developer with deep understanding and practice using git. I agree with you that Issues is terrible though. I tried to use it for my team, but the show-stopper was that you can't move issues between repos, and so there is no way to stay organized across a non-monolith architecture where you need to take issues in based on front-facing products and not just code-level concerns. If it wasn't for that, we probably would have tried to suffer through it just for the integration benefits.

Posted by dasil003 on Jun 25, 2015, 8:45 AM

Tags

• ux (Software)

Related issues

• This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
• I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
• the new VSCode UI, looks cute, i don't like it.
• I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
• The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
• Add PR-style review comments in Git Diff UI that feed into the active agent thread