Ask HN: Thoughts on new GitHub layout?

Post by nyanpasu64 » Fri, Jun 26, 2020, 9:14 AM UTC

foobazzy wrote: post #377

jolmg wrote: post #134

Lots of hate here. I probably don't use GitHub as much as others here, so I can understand that any change adds friction and people are going to hate that. Having said that, I'm comparing using the Wayback Machine: new: https://github.com/torvalds/linux old: https://web.archive.org/web/20200619163555/https://github.co... and I can't find it in me to dislike the changes they've made. They've removed the double repo na…

Tangential comment: I just opened the link with the new design on my phone and it was a delight to look at compared to whatever I saw last time. I think the design changes were made keeping in mind smaller screens, which might be what the user data suggested (how am I to know). But I agree with other comments that the top bar content could be aligned with the rest of the content. Stretching it to each end is causing…

Post by peternicky » Fri, Jun 26, 2020, 6:23 PM UTC

mkj wrote: post #363

natfriedman wrote: post #284

Earlier quoted context omitted.

Thanks for the feedback about the latest commit status. This is something we should definitely fix. Also – I don't think there is a principle of lowering information density at work here. I think it's just a design that we will keep iterating. We are pro information density at GitHub.

The density has increased with things that aren't useful. You're browsing the file listing page ( Code tab) but it now has a bunch of extraneous stuff on the right hand side (Did you know that this repository has 0.5% Perl code??). Also the most prominent bit is the bold #105 in the commit message - who cares about the handcrafted comment, the important thing is the Github specific pull request number.

Post by gillyb » Fri, Jun 26, 2020, 7:08 PM UTC

natfriedman wrote: post #284

ljm wrote: post #126

I submitted feedback over it but, aside from the over-reliance on rounded corners, and making pills and buttons hard to separate, the single worst change is that you can't see the latest commit status from the repo screen. Instead, you get the commit hash, and have to click a tiny ellipsis button to get the commit message and the status indicator. When I'm browsing on github and not using git directly, the commit sho…

Thanks for the feedback about the latest commit status. This is something we should definitely fix. Also – I don't think there is a principle of lowering information density at work here. I think it's just a design that we will keep iterating. We are pro information density at GitHub.

Post by jb3689 » Sat, Jun 27, 2020, 3:01 PM UTC

flowerlad wrote: post #586

natfriedman wrote: post #284

Earlier quoted context omitted.

Thanks for the feedback about the latest commit status. This is something we should definitely fix. Also – I don't think there is a principle of lowering information density at work here. I think it's just a design that we will keep iterating. We are pro information density at GitHub.

Change is bad unless it is great. Don't make changes just because your designers need something to do. When you make design changes your customers must immediately love it, if not it is a bad change. When it comes to design, there is no such thing as a "good change", there are only bad changes (the default) and great changes.

Post by imdsm » Wed, Jul 01, 2020, 1:44 PM UTC

natfriedman wrote: post #284

ljm wrote: post #126

I submitted feedback over it but, aside from the over-reliance on rounded corners, and making pills and buttons hard to separate, the single worst change is that you can't see the latest commit status from the repo screen. Instead, you get the commit hash, and have to click a tiny ellipsis button to get the commit message and the status indicator. When I'm browsing on github and not using git directly, the commit sho…

Thanks for the feedback about the latest commit status. This is something we should definitely fix. Also – I don't think there is a principle of lowering information density at work here. I think it's just a design that we will keep iterating. We are pro information density at GitHub.