it seems they also migrated from server rendered pages, which were a beauty, when you were inspected the network tab. to polymer, which itself, is good and lightweight. Github was one of last big companies not doing heavy spa stuff.
Ask HN: Thoughts on new GitHub layout?
331–340 of 590 posts
Re: Ask HN: Thoughts on new GitHub layout?
#332I don't think it's worth "migrating away" but the new design does feel even flatter to me and the removal of row lines is a step back in readability. I feel like my screen needs further calibrating...
Re: Ask HN: Thoughts on new GitHub layout?
#333Imagine waking up one day and suddenly your apartment is completely different than when you went to sleep. You stumble around, bewildered. You go into the bathroom... and it's the kitchen. You go back and turn left around a corner... and it's not the living room, it's the garage. The entryway to the living room was through the kitchen.
According to the new designers of the apartment you rent, this configuration is much more efficient. Meanwhile, for the next two weeks, every time you want to take a pee, you end up wandering into the wrong rooms looking for a toilet.
Product Owners: please don't treat your users like an afterthought, or refuse to help them adapt to the changes you didn't even ask them to accept. It's careless, and makes users immediately dislike your product.
Re: Ask HN: Thoughts on new GitHub layout?
#334I 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.
Can I ask why did you people bring those design changes - this one and the last instalment as well? Was there some real need, some market research behind it, or just an itch to do something? To be honest both these iterations feel like trying to fix something that's not even broken.
Re: Ask HN: Thoughts on new GitHub layout?
#335Earlier quoted context omitted.
One of the arguments by Designers is that they make the UI more approachable - they don't realize that they are biased by their personal aesthetic taste, their friends like the same type of flat sleek modern UI designs, and they like going to minimal galleries, subscribe to itsnotthat and read the colossal blog. This is a cultural imposition, not something a professional would do. Yet, we have modern designers inject…
True story: my dad is confused by basically all technology and all modern user interfaces. The one site he finds usable without assistance? Craigslist.
Craigslist is the epitome of simplicity. It may not be pretty, but it does what it is supposed to and nothing more.
This practice should be applied universally throughout our lives in every field, perhaps except Art where creativity is revered and the avant-garde prevail.
Re: Ask HN: Thoughts on new GitHub layout?
#336Earlier quoted context omitted.
My hypothesis is the point is to compete with Jira. That would be MS's biggest competitor in this space, and the changes make it look a whole lot more like that. I wonder if MS has gone back on their word to leave GitHub to it's own devices...? I have been unable to find a method to revert. Best option might be to make a bunch of noise. Other than that, it's migration time.
If competing with Atlassian is the point, then they're going to have to completely revise their licensing model for a start. GHE is _far_ too expensive compared to Atlassian's whole software suite to be any real competition.
It gets merged into MS product catalog, GitHub might have a time table at this point...
Re: Ask HN: Thoughts on new GitHub layout?
#337I am really not enjoying the fact my eyes have to move from center where the repo contents are to the top left to see the navigation... I really liked it when it was all centered.
Re: Ask HN: Thoughts on new GitHub layout?
#338Quick hack for Ublock Origin users to get everything lined up again (add this to your filters): github.com#$#body{ max-width: 1280px !important; margin-right: auto !important; margin-left: auto !important; }
That's perfect, thanks! I usually resort to Firefox's userContent.css file, but the feature is now disabled by default, so I'm glad to hear uBO can do it too. Did GitHub only test their new layout on 4/3 screens? It looks so odd when the project header is fluid but the project itself is still centered and 1280px wide. Especially if you log out of GitHub, in which case the GitHub banner is no longer fluid and makes th…
A 13" MacBook would have an effective horizontal resolution equivalent to 1280 pixels. It's likely that they designed this only for 200%-scaled laptops.
Re: Ask HN: Thoughts on new GitHub layout?
#339Earlier quoted context omitted.
Really? I found that I only really look at the code when I look at projects I'm involved in. Usually though I use GitHub for discovery and then I care much more about the languages, commits, releases and Readme.
To be fair, that means you are not the one paying their bills.
I pay them money on several accounts, maybe it's not enough and IBM asked them to do this? I'm not sure how well MS and IBM get along, IBM saw them as public enemy #1 when I left, but where paying for GitHub?
Re: Ask HN: Thoughts on new GitHub layout?
#340I 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.
What about the contrast reduction issues that this design change incurs. Did you think about those of us who have poorer vision? What are you going to do to make GitHub more readable for those with disabilities again?