Live data from Hacker News

Ask HN: Thoughts on new GitHub layout?

news.ycombinator.com

531–540 of 590 posts

Re: Ask HN: Thoughts on new GitHub layout?

#531

Earlier quoted context omitted.

I find it much more difficult now to line up filename and last modified time in the file browser. And I agree on the low density. Plus it now looks like a children's toy, not like a work tool. A while ago, there was an article on HN about kawaii cuteness culture sneaking into everything. It appears that has happened here.

The Kawaiization of Product Design - 33 days ago: https://news.ycombinator.com/item?id=23243646

I started rereading The Design of Everyday Things by Don Norman last night.

They be building Norman Layouts at GitHub

Re: Ask HN: Thoughts on new GitHub layout?

#533
post #498

Earlier quoted context omitted.

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.

I believe for eyesight it's important to change focus, i.e. the distance of the object you're looking to. Not sure if just moving your eyes help but looking up from the screen into the distance is certainly good for the eyes.

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

Re: Ask HN: Thoughts on new GitHub layout?

#534

This 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.

Engagement rate is measurable. The average time it takes for users to complete the action they're looking for is also measurable. Companies test this stuff, Apple isn't spending millions of dollars to redesign MacOS because Tim Cook is bored. Same goes for the Instagram redesign of a few years ago, or this GitHub redesign, etc.

Re: Ask HN: Thoughts on new GitHub layout?

#535

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.

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.

Also there's font-size party happening on the home's right sidebar. 16px, 14px, 12px in a rapid succession.

Meanwhile, on Pull Requests' right side bar everything is rendered in 12px size.

Just to be clear, 12px is equivalent of 9pt. That's fairly small on screen. For comparison the README body text is rendered in 16px, which is equivalent of 12pt.

By the way, HN body text is 13.33px, about 10pt.

Re: Ask HN: Thoughts on new GitHub layout?

#536
post #186
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…

Seems like a bug or probably an oversight. Don't think that was intended

Except that MS Teams is designed exactly the same way.

Re: Ask HN: Thoughts on new GitHub layout?

#539

Earlier quoted context omitted.

Ha, to me it is an improper max width. My biggest peeve with the GitHub web UI is the squished center pane. I hate that it centers it with giant gutters wasting over half the width of a 4K monitor, should I choose to maximize a browser window. I'd much rather see everything shifted to the left. I'd even be OK with some soft margin still causing regular README text to wrap at a typical width. But, if there are long co…

Sorry but do you use full screen windows on a 4K monitor? I doubt any website is really designed to fill anything more than ~1400 horizontal logical pixels.

I don't usually. But if I do, it's because I just encountered something like super-wide content and I want to make use of that big screen. I don't do it because I'd really like to see someone's opinion about how all content should cram into a narrow viewport and have massive blank margins...

Re: Ask HN: Thoughts on new GitHub layout?

#540

Earlier quoted context omitted.

Agreed! Related: I was updating a bunch of dependencies yesterday, and so was going through looking at what's new in a handful where I was behind a major version or more. "Releases" is even harder to find now (it's in the sidebar). I've never understood why it's relegated to a being a sub-item of "code" when it seems to me it should be on the same as information hierarchy level as "issues" "wiki" etc. I'd really like…

I’d love to learn more about this! Why would a top level of Releases be useful?

I think partly it's just the inconsistency that bothers me, but when I'm being a consumer of a project it's one of the main things I look at -- certainly more than many of the other top-level items.

* "Actions" are basically only useful to me as an active project contributor.

* "Security" is a pretty niche tab -- I think personally I've clicked on it only a handful of times, ever

* "Insights" I had forgotten about to be honest (and obviously don't use it), but even as I look at it now, I think it's somewhat useful for judging how active a project. For mature projects (that don't need active development) it says almost nothing. I personally do a fuzzy judgement on Releases, popularity, # Issues open/closed, # merged PRs, # and age of open PRs, # contributors.

I use "Releases" as a consumer in mainly three ways:

1) To help judge the quality and maturity of a project, in terms of how easy it will be to deal with as a dependency. Are releases being used (vs published adhoc)? Are there betas? Is there a changelog or curated release notes? Is semantic versioning being used? How frequent are releases?

2) When updating dependencies, and looking for breaking changes or things I need to update in usage.

3) For downloading, when it's the only way -- though this is typically linked from the main README, and I'd generally only care about the latest.

Post reply on HN