Live data from Hacker News

Ask HN: Thoughts on new GitHub layout?

news.ycombinator.com

411–420 of 590 posts

Re: Ask HN: Thoughts on new GitHub layout?

#411
post #9

They are following the trends of flat design and rounded corners, which I don’t really mind. I’m more bothered by the fact that nothing is aligned: the GitHub logo, the breadcrumb, the horizontal menu and the issue title are all on different verticals. Looks messy.

the alignment is so jarring its mind boggling how this got shipped.

I felt the same, I installed a custom css user style extension just to fix it. Here's a link to my comment with example before and after along with the CSS needed for chrome or firefox:

https://news.ycombinator.com/item?id=23624292

Re: Ask HN: Thoughts on new GitHub layout?

#412
post #9

They are following the trends of flat design and rounded corners, which I don’t really mind. I’m more bothered by the fact that nothing is aligned: the GitHub logo, the breadcrumb, the horizontal menu and the issue title are all on different verticals. Looks messy.

This was among the first things I noticed. Here it is with vertical lines added https://i.imgur.com/EVSTdLA.png

I felt the same, and even made the same image with vertical lines in my feedback to GitHub while the change was still in the preview stage.

I installed a custom css user style extension just to fix it. Here's a link to my comment with example before and after along with the CSS needed for chrome or firefox: https://news.ycombinator.com/item?id=23624292

Re: Ask HN: Thoughts on new GitHub layout?

#413

Earlier quoted context omitted.

I have a light sensitivity condition; large patches of white really hurt to look at for any real amount of time. Please consider implementing an optional dark variant in the vein of https://github.com/StylishThemes/GitHub-Dark as an option.

It's coming.

Amazing! Been waiting for it for a long time. I spend a lot of time on github!

Re: Ask HN: Thoughts on new GitHub layout?

#414

Earlier quoted context omitted.

> If it was a good design, then people wouldn't complain about it. In that case, I submit that good design doesn't exist. I've never seen a major redesign that wasn't widely complained about.

So you're going to ignore all criticism when you make a huge redesign? There are valid complaints about this. I rarely complain about website design, and this time I am compelled to criticize it.

No. I don't ignore all criticism. I just ignore criticism whose only support is the existence of complaints.

Re: Ask HN: Thoughts on new GitHub layout?

#415
Others have outlined some specific issues such as commit status not bing visible from repo view, but besides a few things like this which will likely be fixed quickly I think it's a cleaner a more modern looking design. It's easy to hate on any change simply because it requires some effort to get used to, but I think this is one of the good ones.

Re: Ask HN: Thoughts on new GitHub layout?

#416
Everything which is a list becomes harder to read / get an overview due to the new width (files, issues, PRs). Color changes don't exactly help either.

But for the diff view, it's great to see more of the line width.

Miss the last commit message and especially the status of it. Seems like a major loss of information to me.

Re: Ask HN: Thoughts on new GitHub layout?

#418
post #117

I have a single major problem with all of their new layouts. They place content at extreme ends of the screen, completely stretched out like a rubber band with No Man's Land in the middle. In this case, the top half is stretched and the bottom half is centred. Completely inconsistent and tiring for your eyes darting around corners of the screen. Example: https://twitter.com/JahedDEV/status/1275532988772683776 I don't…

Just logged into GitHub, freaked out when I saw the redesign, and came straight here to say exactly this. It's unnatural eye movement to look wide for platform navigation, then narrow for README/repository navigation. This is outright bad design. There was nothing wrong with GitHub's UI before, it was probably the closest thing to "perfect" I'd ever encountered. Alongside that incredibly irritating "navigate to code…

Genuinely curious here - isn't it better for eyes to move more? Can moving in unnatural way be a good thing considering most of the time they move naturally? Like a sort fo stretching.

Re: Ask HN: Thoughts on new GitHub layout?

#419
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.

Really hate the second column on the right, which for a long README or documentation does nothing but make it so that there's less room for the text. I frequently use GitHub to store and read notes or to create larger docs, this essentially kills my desire to do any of that and makes me want to move what I have. The information in that column is also extremely low value.

Re: Ask HN: Thoughts on new GitHub layout?

#420
post #363

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.

Agreed about the right column. Distracting and leaves much less room for what matters, typically a README.
Post reply on HN