The design before was targeting developers with a "for work" feel. From a vcs perspective and ci/cd perspective it showed the important stuff. The new file browser is especially bad - being Tritanopia color blind the lack of lines and the folders physically hurt my eyes. But To be honest we all know what this re-design is for. Microsoft pushing Azure Pipelines ( github actions ). The previous github interface was not…
Ask HN: Thoughts on new GitHub layout?
441–450 of 590 posts
Re: Ask HN: Thoughts on new GitHub layout?
#442Re: Ask HN: Thoughts on new GitHub layout?
#443Lots 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…
Re: Ask HN: Thoughts on new GitHub layout?
#444What do people feel about the code at the top (both old and new) The thing I think I want at the top is the readme. If I'm looking for repos I need to know what it is before I look at the code. If it's a repo I'm working on I'm more likely to look at the code locally then the code on github. When I do look at the code on github it doesn't need to be on the front page for me. https://github.com/username/reponame/code…
The vast majority of the time I arrive at a git repository is because I want the source.
Re: Ask HN: Thoughts on new GitHub layout?
#445Earlier quoted context omitted.
I love that it's on the right. It means when on mobile, I don't accidentally upvote something that I meant to collapse.
that's because HN on mobile is bad, not because it's good UI
Re: Ask HN: Thoughts on new GitHub layout?
#446Re: Ask HN: Thoughts on new GitHub layout?
#447Using inspect, I did two things - - removed all the rounded edges - added lines dividing the rows in the files table It looks way better with these two things in my opinion. Maybe someone can create a browser extension which does these things.
[0] https://chrome.google.com/webstore/detail/stylish-custom-the...
Re: Ask HN: Thoughts on new GitHub layout?
#448Well I can tell it's a Microsoft project now. Not in a good way. People almost never like re-designs so maybe it'll feel natural later, it's not terrible. Just sterile and corporate feeling.
Re: Ask HN: Thoughts on new GitHub layout?
#449Lots 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…
While as pointed out above the decision of making the top navigation bar span the screen is rather unfortunate, the main thing I see is that instead of the smartphone-centered (or whatever reason) design the central part where the comments are shown is now like 50% wider. Which is something I always wanted because I only use this on desktop and usually with the browser full-screen so finally it takes some advantage of the available space.
However the width used also depends on whether the sidebar is there or not which is quite jarring. I.e. in the toplevel file tree view there's a sidebar. But when you then click on a directory the sidebar is gone and the witdh taken by the tree view expands. That's not ideal and just jarring when going back and forth. So for cases like that, it's not merely the fact there was a change which causes friction, it's really the new version which does.
Re: Ask HN: Thoughts on new GitHub layout?
#450Since this seems to be such a contentious issue, I wonder why they didn't keep the original style around as an option? Aren't stylesheets supposed to make that easy?