It'll take me a few days to get used to it but it's not bad.
Ask HN: Thoughts on new GitHub layout?
371–380 of 590 posts
Re: Ask HN: Thoughts on new GitHub layout?
#372Earlier quoted context omitted.
I think dark mode was a harbinger of dumbed down UI. Instead of spending time on one good UI, designers and developers were forced to make 2 mediocre ones instead. Plus dark mode is easier if you remove all detail and depth from control elements.
I don’t think they built the dark mode version as an entirely new UI, it’s just some css and a class you toggle on the body, making it perfect would require some elbow grease but it’s not a complex feature really.
It's not a complex feature because most UIs have already been simplified and flattened into oblivion. If buttons and controls still had depth you might need two complete sets of assets. E.g. consider what implementing dark mode in iOS 6 might look like.
That's kind of my whole point. Dark mode features are a symptom of UIs that no longer communicate anything significant with color and shade so just changing color with CSS tweaks doesn't break them.
Re: Ask HN: Thoughts on new GitHub layout?
#373[deleted]
Re: Ask HN: Thoughts on new GitHub layout?
#374It seems faster. Quite snappy.
Re: Ask HN: Thoughts on new GitHub layout?
#375Aside from the accessibility concerns -- which is honestly inexcusable -- the non-centered repo layout is so strange to me:
All that info that's now in the sidebar is temporary. All of it. I never need to look at a project language more than once.
However, it takes up 100% of the height of the page, so when I'm halfway through a README, the README gets offset by some magical space. The ghost of the 1 paragraph of "language/tags/etc." takes up that space. The README is not centered.
From a design perspective, this layout implies an equal level of hierarchy between the right sidebar and the main content. It implies that they should be referenced side-by-side. But that is just not the case. I want to meet the person who thinks that the document literally entitled "README" (or oh, I don't know, all of the files) is somehow as-or-less important than the tags on a repository -- which are usually just the title copy pasted anyways.
I develop open-source things and I absolutely love to use GitHub. In particular, I've spent a LOT of time reading README's and also writing them. I really think their centered layout should come back.
As a suggestion: Maybe they could shift just the _files list_ over for that sidebar, and have any block content not centered?
Or maybe if there somehow existed a compact way to organize that information. Maybe a horizontal layout because there is only a little bit of text. Something like that.
Re: Ask HN: Thoughts on new GitHub layout?
#376I 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.
Started a thread on twitter to see if we can get more questions answered or an answer to when we might
Re: Ask HN: Thoughts on new GitHub layout?
#377Lots 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 pain.
Re: Ask HN: Thoughts on new GitHub layout?
#378This is the MacOS 11 thread all over again. Apparently no one on HN has been through a redesign... For those of you complaining, congratulations, you've discovered ~ nostalgia ~ In two weeks you'll inevitably find the old design ugly, and forget GitHub ever looked any other way. In 5 years, each will get another round of improved designs, and there will be a thread on HN full of people complaining about how the new d…
That dumb wall of text simply to show you don’t know what the word “objectively” means.
It’s also telling that so much of this “objective” user experience narrative apparently depends on immediate and gratuitous condescension and hostility towards your users.
You sound like a complete asshole. You’re not better than everyone that disagrees with you. Try to do better.
Re: Ask HN: Thoughts on new GitHub layout?
#379Earlier 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.
Why aren't you doing A/B?
What would be the evaluation metric? Certainly measures like "engagement" could give exactly the opposite signals - hide everything behind more clicks and you'll get a lot more clicks!
Re: Ask HN: Thoughts on new GitHub layout?
#380Earlier 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.
It's great to read this comment - it's always nice to know that community suggestions aren't just cast into the void
Reminds me of when HN added the [-] and everybody complained it was on the wrong side but they couldn’t be * to fix it.