30 ms·
Ask HN: Thoughts on new GitHub layout?
I think it feels like Jira and I'm really sad. Seems more like a MS move than a GH move...
Migrating to gitlab...
- amadeuspagel 6y agoI don't see what's wrong with it. One thing I love about it is that I can now finally read readmes even if the window is only half or even a third of the width of my screen. Other then that it just looks a bit more modern. One thing I just slightly dislike is that the width of the body is limited, but not the width of the header. Looks inconsistent.
- verdverm 6y agowait, how do you find readmes easier now? They used to be full width no matter how wide your window was (I put to 1/2 for browser). Now they only occupy 70% of that space. So I just lost 30% of my readme width to empty space. This is just terrible UX
- WorldMaker 6y agoGitHub never had full width pages before of the Repo interface. They used a giant gutter on both sides on widescreens in classic Web 1.0 blog template fashion. That ~30% empty space has always been there beside the README, it's just now consolidated to a single side and used to bring a few more bits of information "above the fold".
- rowanseymour 6y agoIt's not the layout I dislike but the styling which makes it harder to see what is a button and what isn't, e.g. only 2 of these are clickable https://imgur.com/a/wR9xsvT https://imgur.com/a/wR9xsvT
- slmjkdbtl 6y agoReminds me of sr.ht who just straight up make every link blue + underline, on the scale of design effectiveness it already beats 99% websites
- qqii 6y agoExample repository of a project that's invested in using GitHub: https://github.com/NixOS/nixpkgs https://github.com/NixOS/nixpkgs Discussion on /r/github: https://www.reddit.com/r/github/comments/hei81f/ https://www.reddit.com/r/github/comments/hei81f/ Personally I think it's an improvement on mobile - finally the entire README is readable by default. That being said was there any warning/reasoning behind the change? I cannot find any announcements.
- misnome 6y ago> That being said was there any warning/reasoning behind the change? I cannot find any announcements I had a "Preview: Try the new layout and give us feedback" notification for about an hour, then it switched on permanently. Optimistically, maybe they accidentally flipped a trial feature flag globally and it wasn't intended?
- verdverm 6y agoI tried out the preview several days ago and let them know what I thought. It's more telling that they didn't listen and pushed it out so quickly anyway.
- h91wka 6y ago> Personally I think it's an improvement on mobile ...because usage of Github from mobile is so important /s
- blondin 6y ago
- misnome 6y agoUgh, they've gotten rid of the commit message, because they merged "commits" "branches" "tags" into the header bar. If you want to see what the latest commit was you need an additional click. Turns out that glancing at the header was useful to tell what was going on! On the plus side, GitLab's repo view (which I disliked because it felt cluttered and always hard to find what I wanted) is now easier to use and read than GitHub's, so that makes changing easier.
- misnome 6y agoAlso, I'm noticing a lot more "preload" pages ... e.g. the page loads with blank placeholder fields for the commit and text information that's then replaced live after loading the page. Maybe it did this before and is just slower now?
- verdverm 6y agoyup, this is a Jira move, GitHub sounds like it's on it's way down fast
- misnome 6y agoMy cynical guess is that they used “page load time” as a metric to prove their new system was “faster”. And maybe only tested internally on a faster system, or with hot-cache repository loads? It doesn’t seem to do it on reloads, though going away for a bit and coming back seems to cause it again (and, visibly, different parts of the page load at different times). Anyway, It definitely reeks of “enterprise” so I guess Microsoft finally got enough people into github to steer the ship towards the iceberg.
- verdverm 6y ago> reeks of “enterprise” you made my day! thanks
- acemarke 6y agoAs I just said on Twitter [0]: > Hrm. I just got switched to Github's new look and feel... and tbh, I _don't_ like it. I liked the 3D depth of the prior buttons. The new ones are too flat, the text is thinner, and they're too rounded. I appreciate that people worked on this, but... why was this change needed? (See tweet for a screenshot comparison of the "New Issue" and "Edit" buttons before and after) [0] https://twitter.com/acemarke/status/1275465823403020288 https://twitter.com/acemarke/status/1275465823403020288
- RileyJames 6y agoHmmm. The new design seems to be pushing hard towards "dev in the browser" with the new. "Add file", which forks the project, and drops you straight to editing a new file, ready for commit. Kinda interesting. But beyond a README, I can't imagine making any significant edits this way.
- conradfr 6y agoThe picture on the profile page is so comically big. I'm not sure what was wrong with the old design. Now everything is too rounded and flat and there's not enough contrast. I also liked GitHub better years ago when the top bar was not black, so yeah I can hold a grudge :)
- juliendc 6y agoThey 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.
- verdverm 6y agoThe grayscale reduction and loss of contrast is a modern design anti-pattern they have adopted. Makes reading things more difficult
- rowanseymour 6y agoWe'll all get used to it, but it's harder now to see what is a button and what isn't, e.g. only 2 of these are clickable https://imgur.com/a/wR9xsvT https://imgur.com/a/wR9xsvT
- rurp 6y agoWow, that's pretty bad. Logical consistency was clearly not a guiding principle of this redesign.
- roryokane 6y agoThere is a consistent principle behind those choices: rectangles with slightly rounded corners are clickable, while rectangles with semicircular sides (“pills”) are not clickable. It's confusing because I've never seen another site that distinguishes clickable elements in that way, but I can imagine we'll grow to find it intuitive with enough usage.
- rowanseymour 6y agoFor sure we can all learn through trial and error pretty much any UI. And I know there are complaints any time any big site tries to do a redesign. But a good UI should be intuitive for a first time user. This seems objectively worse.
- yboris 6y agoI love it ¯\_(ツ)_/¯
- taylorlapeyre 6y agoI really like it!
- verdverm 6y agowhat about it?
- rurban 6y agoLike it. More important links upfront.
- verdverm 6y agoDetermining which language the repo is now requires scrolling, as now the readme is only 70% width instead of 100% So much wasted space and loss of information if you ask me.
- DenseComet 6y agoThis is my biggest gripe with it. The sidebar only extends down for a short length, but causes the entire readme to shrink and results in a lot of empty space. I'm indifferent to all the other changes but the readme shrinking for no good reason is quite annoying.
- rozab 6y agoYep. The languages used in the repo is the first bit of information I look for. That little visualisation was a very clever feature and a highly efficient use of space.
- phillipcarter 6y agoI'm completely neutral. They've changed their UI many times over the years and this is no different. Products usually change UI and that's just a fact of life.
- verdverm 6y agoThis is different because there was a major change to where (formerly header) information is displayed now on the side. The top-level hierarchy is different and causes much more wasted space
- phillipcarter 6y agoHonestly, I don't care about any of these things. UIs change and I just have to deal with it.
- threeseed 6y agoI will never understand people who take the time and effort to post comments saying "I don't care".
- gruez 6y ago>They've changed their UI many times over the years and this is no different. Products usually change UI and that's just a fact of life. Your justification for bad redesigns is that... other companies do it too? That's a very apathetic/defeatist attitude.
- dntrkv 6y agoMost of the time it isn't bad UI but a vocal minority that just hates any change. It's not like these companies release these changes without doing significant user testing and AB testing. If you design based on the opinions of HN/Twitter, every site would look like Craigslist (or HN's favorite abomination of a design, the Berkshire Hathaway site).
- elchin 6y agoI like it, better use of horizontal space.
- verdverm 6y agoHow is it better when there are large swaths of empty space? Like scroll down a readme, is all that space on the right better usage?
- lukeramsden 6y agoI generally liked the new design in the feature preview, except for the new repo page, which I immediately opted back out of. The "About" being moved to the right side is a good move, but the top bar being full-width is incredibly annoying. If this is any taste of things to come, then I imagine I'll be moving to Sourcehut permanently earlier than I thought.
- verdverm 6y agoI've actually been thinking about GitLab since Sid interviewed Joe Jacks. https://www.youtube.com/watch?v=jk_DNX8LGuM https://www.youtube.com/watch?v=jk_DNX8LGuM I'm thinking of moving just to support another COSS (Commercial OSS) company. https://coss.media https://coss.media
- Sachaniman 6y agoSign up for the developer feature previews, so you can give feedback to these changes before they're published. I gave some negative feedback about it earlier regarding this change, but it seems I might have been a part of the minority.
- verdverm 6y agoI gave negative feedback as well during the preview. Really love that they ignored it...
- ithkuil 6y agoPerhaps they got more positive feedback from people other than you?
- bcrosby95 6y agoNot necessarily. I've seen the concept of "vocal minority vs silent majority" used as justification to push through a change. So even if you get only bad feedback, it still goes through because most people said nothing, which means most people like it.
- ithkuil 6y agoOr most people hated it but didn't love the product enough to care to comment. Perhaps the design of the feedback form matters. I wasn't part of the beta so I don't know how they asked.
- deleted 6y ago[deleted]
- verdverm 6y agoThey didn't ask, you have to go into the feature view menu (under profile) and then click a link there to go to another page and then have a form to fill out. They know UX for sure! Maybe we should send them a copy of Don't Make Me Think
- jventura 6y agoIt looks more like gitlab!
- verdverm 6y agoI don't see this sidebar on the repo page in GitLab. Jira has this, thus my association and triggering ;]
- somerandomacc 6y agoLike many others, I use Github every day. Changes like this add friction to our workflow. There better be a damn good reason for these changes, otherwise it's a pointless redesign that looks no better than it did previously while simultaneously adding a slight overhead as users "learn" the new layout. Does anyone know of an option to revert this update?
- verdverm 6y agoMy 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.
- eyerony 6y ago> My hypothesis is the point is to compete with Jira. When they start making everything drag & droppable at a huge cost to UI latency and bundle size (plus, for some reason, idle resource use), we'll know for sure that's what they're doing.
- talideon 6y agoIf 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.
- carlosdp 6y agoHonestly, it's a positive improvement. Better information layout, and the code is still front and center. None of the core functions really changed place, just changed padding a little.
- verdverm 6y agoWhat about determining the language and license? That used to be front and center and two of the most important things when I land on a repo page.
- carlosdp 6y agoI highly doubt that's the case for most people when using Github on a daily basis though.
- t0astbread 6y agoReally? 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.
- lostmsu 6y agoTo be fair, that means you are not the one paying their bills.
- verdverm 6y agoI 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?
- t0astbread 6y agoFair point. Although I do wonder how enterprises manage their dependencies. Do they not use GitHub like that at all?
- h91wka 6y agoLooks absolutely horrible. I use a laptop as my main dev machine, and all these 16px and 30px paddings that they added everywhere create real tunnel vision experience. I guess people with huge displays don't mind... But I absolutely do. Looks like another case when a frontend team does something to justify their existence. But let's look at the positives: the last redesign of that sort helped me to completely migrate away from gmail.
- verdverm 6y agoYeah, maybe I am a minority in viewing web pages in 1/2 1080P? The only screen that is full screen is the code. But really, I want to look at two windows without issue on the same screen. Is that so much to ask? Can we have better layout on 1/2 1080P screens please?
- verdverm 6y agoSo much of modern design seems to be more about / for the designers than the users or UX. Maybe they need a good introspective period in their art, or some psychology classes?
- Nextgrid 6y agoI don't understand the appeal in this for the designers either. Back in the old days (~2010s) every UI had some personality and very intricate details that the designer would be proud of and that will differentiate them from the competition. Nowadays it's the same flat, white and empty UIs everywhere - there is no significant difference. Would a designer really be doing their personal brand a favour by putting one of these new "designs" on it?
- eyerony 6y agoThe appeal is that they need something on-trend to put in their portfolios for career advancement. It's their version of résumé-driven development. Project managers have similar incentives (screenshots are very powerful, in many settings) so at least don't stop them, if not actually encouraging them.
- verdverm 6y agoAnother concurrent thread https://news.ycombinator.com/item?id=23616422 https://news.ycombinator.com/item?id=23616422
- dang 6y agoWe've merged it hither.
- Stevvo 6y agoI'm not sure yet, 30 minutes isn't long enough with it to form an opinion. My initial reaction was, What? Why has this changed? I didn't see anything wrong with the old one. I do like that sponsors appears more prominently; for a very long time financial incentives have been an unsolved problem in open source.
- Dowwie 6y agoI've been really happy with Github Dark: https://github.com/StylishThemes/GitHub-Dark https://github.com/StylishThemes/GitHub-Dark I can't relate to the OP's preference for Gitlab's UI. Gitlab UI is the reason why I don't use Gitlab.
- verdverm 6y agoI don't have preference for GitLab. I do not like Jira, and if GitHub starts to be Jira, definitely looking elsewhere. GitLab seems like the next best option. Any other suggestions welcome too!
- dugmartin 6y agoA little weird that the top nav in a repo is flush left instead of using auto margins and a max-width like the rest of the page under the nav.
- efiecho 6y agoUgh, that's not good. Latest commit message and date will not display under <> Code without Javascript enabled, but if I click around in the repository and go back to <> Code or keep refreshing the page, they suddenly show up, still with Javascript disabled. Can anyone explain this? However, I do like the visual part of the new layout.
- recursive 6y agoI don't see commit messages inside the "Code" menu item anywhere, with or without javascript or reloading. You have to click a commit hash to see its message. I think this is an improvement.
- martinesko36 6y agoI hate it. It nixed any contrast.
- verdverm 6y agoRight, like this is such an obviously bad design pattern and yet they still do it. I just don't understand where design is as a science or art anymore...
- martinesko36 6y agoIt is redesign for sake of redesign unfortunately. My guess is GitHub/MS has a bunch of designers paid full-time and they need to justify their salaries.
- s9w 6y agoWhere did releases go?
- bluefox 6y agoI've been using GitHub since 2008. My default browser has JavaScript disabled for various reasons. It was not long after Microsoft acquired GitHub that the UI changed for the worse, but it was minor and still very functional. Now, it's terrible: the dates and commit information is missing, for example. I expect soon it will reach GitLab "quality": unable to view source code without JavaScript enabled. I'm still on the fence on whether to act on it now, for my own projects, or wait for the fatal blow. Since much of the programming world is on GitHub, this looks pretty bad for me.
- efiecho 6y ago> I expect soon it will reach GitLab "quality": unable to view source code without JavaScript enabled. I also hate GitLab for this, but I learned today that they are actually working on fixing this, by shifting some components to server side rendering. Awkward for me if GitLab suddenly will become the better choice.
- bluefox 6y agoThe way it looks now, a self-hosted gogs with a nojs patch may be the way forward. The application-specific part (gogs.js) is <2kloc and it's already rendering stuff on the server. I'm giving it a few weeks before I've had enough...
- j-james 6y agoYou could also try out Sourcehut, which seems to fit your use case well. https://sourcehut.org/ https://sourcehut.org/
- arghblarg 6y agoI selfhost gogs and like it. And the releases link is at the top like many ppl wish here :) Only thing I really miss vs. github is there's no code review built-in.
- j-james 6y agoThat's cool, I'm looking forward to that. Since many different organizations self-host GitLab instances (which is great!), having to enable Javascript for each one can be a bit of a pain. https://gitlab.com/gitlab-org/gitlab/-/issues/215365 https://gitlab.com/gitlab-org/gitlab/-/issues/215365
- Rochus 6y agoThe number of repositories is no longer displayed, or did I miss it?
- mscdex 6y agoQuick 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; }
- Kyrio 6y agoThat'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 the project header look really out of place[1]. [1] https://imgur.com/3wOE7Nr https://imgur.com/3wOE7Nr
- ntauthority 6y agoA 13" MacBook would have an effective horizontal resolution equivalent to 1280 pixels. It's likely that they designed this only for 200%-scaled laptops.
- frant-hartm 6y agoThis should be to most up-voted comment.
- tmabraham 6y agoGitHub what have you done? I feel GitHub is making a lot of changes in a short amount of time and as someone mentioned earlier, it really leads to additional friction in our workflow. When we get used to one layout and then they change it, there is time and effort required to get used to the new layout. It's fine if there is some clear benefit, but I don't see any such benefit in this case...
- throw_m239339 6y agoIt doesn't look good, but it's not that bad either. But I don't think GitHub needed a layout change on desktop screens. They should increase the margins a bit.
- riccardogiorato 6y agoA list of feedbacks on the new UI here: https://www.reddit.com/r/github/comments/heknhd/some_real_feedback_on_the_new_ui_changes_tweets/ https://www.reddit.com/r/github/comments/heknhd/some_real_fe... Personally I would love to see some fixes to the project page where with the new Design you waste ton of space on the screen for things that you could see before just in a small row now they take 20/30% of the right part of the screen just if you don't scroll and if you scroll down you get 50% of the screen or more just white...
- floatingatoll 6y agoWhich of these changelog entries are you referencing? https://github.blog/changelog/ https://github.blog/changelog/
- achr2 6y agoWhat a poor design, yikes. Did they seriously just use an off the shelf 'responsive' template and not think twice? We are programmers, this is code - give me information density!
- sdinsn 6y agoI don't like it. I thought the old layout was pretty much perfect, no need to change anything.
- The_rationalist 6y agoNeeding to scroll horizontally on a phone is an intolerable regression.
- arch-ninja 6y agoTools which change like this never stand the test of time. A far better move would have been to standardize GH APIs and provide native clients, guaranteeing long-term utility on many platforms. Git passed the test of time, but github likely will not. Edit: today I learned a lot of young people sound like old people. Interesting perspective.
- scottoreily 6y agoOkay boomer
- yadco 6y agoReminds me of gitlab
- diob 6y agoI think I dislike the new repo view because the two main columns are reversed from what my brain thinks they should be. Did a quick jumble of the html and css to things I would prefer: https://imgur.com/a/1HEROxa https://imgur.com/a/1HEROxa Not perfect but I like it more than what they went with.
- karmakaze 6y agoI thought you all were exaggerating. So sorry not. The commit list looked like it was doing some sort of eventual consistent update, then I realized that hovering over different commits expands that one shifting rows up/down as you hover on different items. GitHub: under new management. My theory about management is like my theory for bad music at venues. The management greenlights which acts will play, unfortunately most owners don't have a clue, they themselves are not the target audience. There are also legendary venues where obviously they were 'in the know'.
- jamespetercook 6y ago> “ There are also legendary venues where obviously they were 'in the know'.” Could you elaborate on this?
- rurp 6y agoI took it to mean that most music venues are managed by people who don't know or care much about the music they book; however the best ones are run by competent people who are also passionate about the music. It seems like a pretty good analogy to me. A lot of UI redesigns (including this one) seem like they were approved by people who liked the look of some static mock-ups, but weren't regular users of the site. Lots of layouts look great in a demo but are awful to use.
- karmakaze 6y agoYes exactly what I meant. Even the changelog summary is similarly directionless: > Today we’ve launched a refresh to the design of GitHub UI, and layout changes to your repository homepage. We hope these changes improve your experience visiting and maintaining repositories, and using GitHub in general. Along with visual design changes, you’ll see the the following updates to your repository homepage: - Responsive layout and improved mobile web experience - More content surfaced via the repository sidebar - Ability to show or hide Releases, Packages, and Environments in your repository sidebar > These changes lay the foundation for future incremental improvements that will better surface your projects, the people who make them extraordinary, accessibility, and yes, dark mode. The whole thing reads like it was an update to a landing page, which it is for some projects. But it's also a core point of collaboration and workflow for many, not to be rearranged without precise and deliberate intention for each and every change. A "refresh to the design" rebrand to signal new ownership is not welcome. Edit: it's even really bad as a landing page. I just realized that the README is now often 'below the fold' because of so much linespacing whitespace above it. The 'refresh' was clearly meant to be for its own sake and any improvements secondary or incidental.
- greatgib 6y agoIndeed, that is shitty cloggy. Yes a MS or Google move where you break something that works well because of product managers that want "new things" to sell.
- zowanet 6y agoI don't like change. I don't like the circular avatars - I don't need the place I store my code to feel like a social network. But the worst change for me is that the 'Languages' section is now below the fold. Now I have to scroll to find out if I should ignore the latest compiler, package manager or system tool because it was written in JavaScript. Edit: Gah! I only noticed this by directly comparing old and new, but the filenames in the main list are no longer blue, so now on each row, the filename, commit message and timestamp are in three subtly different shades of gray. That, combined with the lack of gridlines just makes the whole thing look like word soup.
- thex10 6y ago> the filenames in the main list are no longer blue, so now on each row, the filename, commit message and timestamp are in three subtly different shades of gray Shoot, now I notice it too. I like the redesign but that is just.. bad.
- RampBiggety 6y agoYeah, slamp biggety, and gosh damn, of course, I just noticed A COMPUTER flying by our apartment. Goggedy Goops. Gosh damn. I can just swear it happened. Giggety gloops. Did anyone get that. God swearn. It just flew past over. G'd'mohn. I just don't know what to say. It's just. Uneasy to explain.
- fireattack 6y agoAgreed. Language color bar is one of the most iconic and useful design of GitHub IMO (not sure if GitHub invented it though, since GitLab has it too). It's a shame it gets moved.
- swilliamsio 6y agoI completely agree with you that the stats and language bar were iconic and quintessential of GitHub. It is a massive shame that it's effectively been removed.
- onnnon 6y agoI like it. Wider content, improved IA, cleaner graphics, and mobile support. I can see people not liking the repo nav being fullscreen with very wide monitors. Maybe an option to pin it to the content width would be useful.
- gscho 6y agoWhen I logged in today and saw the redesign I thought to myself, "how long until there is a hacker news post full of comments blasting this"? Thank you for not disappointing.
- anonymousab 6y agoI'm not the biggest fan, but the site seems functionally much faster on the massive repos I'm working with. Overall a net benefit.
- azangru 6y agoWonder how it performs on definitely_typed :-) UPD: Nah, it can't handle it.
- sloreti 6y agoFrustrating that it no longer shows the latest commit message at the top by default.
- recursive 6y agoI'm not frustrated. In fact, I prefer the cleaner look. Now I'm not distracted by extra information I don't care about 99% of the time.
- AlexandrB 6y agoThis is getting cliche. With any modern UI redesign you can immediately guess what's changed: * Removed/reduced visual separation between elements * Flattened things more * More padding Modern UI designers are strikingly unoriginal.
- knoebber 6y agoDon't forget: * Added dark mode
- AlexandrB 6y agoI 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.
- ericmcer 6y agoI 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.
- AlexandrB 6y agoIt'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.
- hombre_fatal 6y agoThere isn't a color scheme you can pick where you won't get users asking you for a dark-on-light vs light-on-dark version, whatever is the opposite of whatever color scheme you thought would be one-size-fits-all. Though you seem to be suggesting that's somehow a bad thing and I'm not sure why. Dark mode is so popular that operating systems have even started supporting a native toggle.
- MikusR 6y agoThey destroyed the one thing Github had over alternatives (like gitlab). An easily findable releases section.
- internobody 6y agoThis is my largest complaint (so far), since it was something I was looking for on a project just after the release.
- jolmg 6y agoI don't really use the releases section (don't recall it existing, to be honest), but right now it's among the first things I saw when going to a repo. It's in the new sidebar.
- driverdan 6y agoThere's are large release section at the top of the right column. It's given more real estate now than the simple link that was there before.
- MikusR 6y agoPreviously it was at the top in the same row as Code, Issues etc. Now without scrolling it is at the bottom right corner.
- tom_ 6y agoIt was a sub-heading in the Code section. See, e.g., https://web.archive.org/web/20200320205539/https://github.com/torvalds/linux https://web.archive.org/web/20200320205539/https://github.co...
- rvz 6y agoThey also placed the 'About' on the side bar which of course messed up the mental model for lots of Github users, judging by the comments here.
- saagarjha 6y agoWow, they rolled that out quick! I think they were pushing the beta just a week or two ago…
- verdverm 6y agoYeah, I think they forgot to take the time to listen to their users
- blondin 6y agoyea, i activated it in feature preview for about about a week or so. i love the new UI! i honestly don't mind the flat design and the spacing. the UI is truly responsive now. that's what i care most about. they finally made it possible for me to read code at my specified zoom level. it's something that i struggle with on a daily basis on many websites.
- thegabez 6y agoWorst UI update to GitHub I've ever seen. Reminds me of GitLab. Who thought this would be a good idea? Shame, they could have used the resources for updates that would actually make GitHub better.
- fuzzy2 6y agoThis looks nothing like GitLab.
- whalesalad 6y agoI've been previewing this for a while. My biggest gripe is the treatment on all of the buttons. They look like they are depressed when they aren't and don't stand out as remarkably as a call-to-action the way the old buttons did. The easing on the hover animations is way too slow, as well. It just feels half-assed.
- carlosdp 6y agoI think it's fine, nothing much actually changed...
- azangru 6y agoI agree. I was afraid I was gonna hate it, but it left me largely indifferent. More white space, rounder buttons, round avatars, wider and more centrally positioned content area, new icons, slightly different colors. Whatever.
- deleted 6y ago[deleted]
- a_bored_husky 6y agoA small bookmarklet that improves the design in my opinion javascript:void(document.getElementsByClassName("gutter-condensed")[0].childNodes[3].after(document.getElementsByClassName("gutter-condensed")[0].childNodes[1]))
- atarian 6y agoIt looks OK, but I hate how the header is now justified to the edges instead of being centered.
- saghm 6y agoDitto, and doubly so for the README. If I'm scrolled down further than the end of the sidebar, the README, suddenly 40% of my screen is empty, and not even split evenly on each side.
- eyerony 6y agoOh is that what it is? I was trying to figure out why it looked so bad when not zoomed uncomfortably far "in", when I didn't recall that ever being a problem before. I think that's it. Ugh now I can't un-see how much farther it is to mouse from the repo "body" to menu items (including those associated with the repo, which are now, confusingly, disconnected from it visually) now. Thanks for that.
- rvz 6y agoIt's never been a good time to try something else. That something new is GitLab. GitHub however, capsized one of its servers yesterday resulting in downtime for some including me and today I wake up to this horrific eyesore that Github has blasted onto my screen, which I can't revert or disable. It now looks like a shameless rushed copy of the GitLab look. I'd rather use GitLab for real instead.
- kostarelo 6y agoI really like it, it's much more cleaner and despite all the comments in here, I find it to be a very smooth transition. I wondered around for a few minutes and pretty much mapped the whole changes. I really don't get what's all the fuzz about.
- granzymes 6y agoLooks like nothing I use regularly moved too far away. I like the new top bar (I'm sure this will make it more mobile-friendly). One change I would make is to give the README section a header so it is easier to see where to stop scrolling if you are trying to get to it. Overall a positive change since the pages are loading faster for me.
- Hedja 6y agoI 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 https://twitter.com/JahedDEV/status/1275532988772683776 I don't know why they think it's good design, it would be nice to know. All of their previews for it squash the window so it looks perfect, like their mockups I assume. Similarly, I have to have a dedicated, half-width window just for GitHub to workaround this.
- dgellow 6y agoYep, I have the exact same issue. I started to use the new design via their beta program, I had to stop after a few days because the content stretches from one side of my screen to the other. I hoped they would fix it before release.
- AOsborn 6y agoAgree completely. Feels like a huge step backwards. Maybe usage metrics show most users are using a much smaller window size, but the layout is all over the place on my 27" monitor (2560x1440).
- giancarlostoro 6y ago> Maybe usage metrics show most users are using a much smaller window size, but the layout is all over the place on my 27" monitor (2560x1440). Some of us like to code with git / bitbucket / gitlab side by side with our IDE so we can reference existing issues more directly while writing code. Which reminds me I need a better screen resolution... 1080p is so 2016.
- threeseed 6y agoThe problem is your resolution. I have a 4K monitor and have Git/IDE side by side and the layout is a real problem. It's 30cm/1ft between the Issues button and the main table.
- Kiro 6y agoLike with every redesign everyone will eventually get used to it and completely forget how the old one looked. When the next redesign happens everyone will rage the same way and say they want the "old" design back.
- DreamScatter 6y agoWrong, this redesign is awkward. If it was a good design, then people wouldn't complain about it. However, it really is a step backwards.
- recursive 6y ago> 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.
- DreamScatter 6y agoSo 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.
- recursive 6y agoNo. I don't ignore all criticism. I just ignore criticism whose only support is the existence of complaints.
- Kiro 6y agoThe difference is that it's about a service you use a lot so you automatically get conservative and defensive about the design. This is no different than people joining groups on Facebook "WE DEMAND THE OLD DESIGN BACK" every time they do a redesign.
- Kiro 6y agoThis happens with every redesign so no, your assumption that complaints automatically means it's a bad design is wrong. Just wait and see. It won't be long until everyone (including you) have completely forgot about the old design.
- deleted 6y ago[deleted]
- brailsafe 6y agoYou'd switch platforms just because you don't like the layout?
- ljm 6y agoI 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 short-hash is the last thing I care about. You cannot see if your default branch has passed CI/status checks now. Those things should be first class citizens, that's why we put status badges all at the top of our readmes to make that info more visible with what we have. It follows the trend of designing with lower information density. This trend IMO is not appropriate for developer tools.
- blueline 6y agoyep. this and the change to the file browsing, where the lines that delineated files/folders are now gone, causing me accidental misclicks of the wrong file, are two very glaring annoyances. everything else i feel neutral on
- JoshTriplett 6y ago> 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. Omitting the commit message is a net improvement to me; I've found that the commit message of the random commit that happens to be at top of tree is completely unhelpful for someone browsing the repository, and especially someone new to the project. However, showing the status indicator inline does indeed seem like a good idea. That said... > You cannot see if your default branch has passed CI/status checks now. If it hasn't passed CI and status checks, it shouldn't be in your default branch. (There are cases where periodic status checks may get re-run after merging, such as checking if your default branch builds with more recent versions of software than it was originally tested with. But the normal CI and status checks should run before merging.)
- ljm 6y agoIt's not so clear cut. Most places I've worked, we don't build artifacts (docker images, whatever) until there's a merge to master or a tag has been pushed. This automatically means that even though your tests remain green, you still want the status check for the stuff that isn't relevant inside a PR. For us, if the status is red in master, it doesn't mean the code is wrong, it means something went wrong in the deploy pipeline.
- tomklein 6y agoI actually like it but I miss the small bar at the top containing the links to the releases, commits, language information etc. in a single place. However, I have a quiet big display with great color settings and didn't try it yet on my smaller laptop displays. I guess if your display doesn't show the light grays and shadows as well it may suck.
- deleted 6y ago[deleted]
- jolmg 6y agoLots 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 https://github.com/torvalds/linux old: https://web.archive.org/web/20200619163555/https://github.com/torvalds/linux 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 navbar in favor of just 1. They've added a right-sidebar that shows various info about the repo in general, like what the last release is. Before, I would open the branch/tag list to look at the versions; now, it's plain as day in the sidebar. For the main contributors, I no longer need to go to insights > contributors. They're shown in the sidebar. For the main languages, I no longer need to click on the thin color line. I find that the most common bits of info about a repo that I sought are now displayed in the main repo page. That's an improvement. I don't understand why people are complaining like it's an absolute disaster. It's not perfect, sure, but this seems to bring significant improvements.
- treve 6y agoAlso fun to go back to a much earlier version: https://web.archive.org/web/20130807124247/https://github.com/torvalds/linux https://web.archive.org/web/20130807124247/https://github.co...
- granzymes 6y agoHah. I think we can all agree that the UI has been improved since then.
- nfoz 6y agoI....... have to disagree, though I'm not sure why, but that old one looks much better to me. Like it's simpler and more clear.
- jolmg 6y agoThe sidebar it had seems to waste too much space, though. It's just 5 links meant for navigation. They'd be better arranged horizontally. I can agree that it's clearer than what we had a few days ago, having only 1 navbar instead of 2, but that's also because it has a lot less features than GitHub has now.
- DreamScatter 6y agoThe new web design layout on GitHub is awful and has less accessibility. For example, the repository languages used to be at the top center of the page, while now I need to scroll past the bottom of the screen and find the information off centered in an awkward place. The stars and other top bar links are off centered in an awkward way for the mouse and the eyes. Also, the profile tabs are less accessible because followers are now on the other side of the screen instead of in the convenient tab location. Please contact GitHub with your feedback if you also think it's less accessible design.
- duhi88 6y agoI wouldn't consider any of your criticisms as being "less accessible". To take your example of the languages, the new design is more accessible. It has a clearly labeled heading, and I can see the names of the languages are being used without clicking on the bar. The old design has no hints that the striped bar (or in the case of `linux`, grey) is supposed to be informative. We're all just used to clicking that bar if we're curious. It's clear they've optimized the layout around productivity, and making it more approachable to new visitors. Everyone has their preferences, and new designs are always tough to get right for everyone. "Less accessible" is the wrong way to phrase your criticisms, though.
- DreamScatter 6y agoThey could have left the languages in the same place where it was before. Now it requires extra input and mental effort to find the languages section. This is definitely a step backwards. Not complaining about the design of the new languages section, but the layout is just completely terrible and useless.
- jamespullar 6y agoI would regularly wow people by showing them the language feature existed. It was obfuscated in the old layout and now it's readily available without any additional clicks. Yes, my eyes have to scan to the side now, but to call it "completely terrible and useless" is ridiculous. More users will discover this feature now that it's been moved and made visible.
- deposition 6y agoThere's not enough contrast compared to the old design.
- geori 6y agoIt looks like Gitlab. I wondered if i was on the correct site.
- traverseda 6y agoI don't like change. --- Alright, that's a big of an exaggeration but I don't feel like this change is nearly good enough to warrant significant changes to a professional tool I use. Like if you want to completely change my user-experience you better at least have a reason, not just do it for-the-lulz. After trying it out for a while under the feature preview I really don't get why they did this.
- disposekinetics 6y agoWhy is there so much wasted space?
- llacb47 6y agoToo wide and spacious
- alfg 6y agoNot a fan of the new rounded corners on everything. Also, don't like how a repository's navigation is no longer aligned with the content of the repository itself. Just seems off. Other than those two, everything else seems OK.
- duderific 6y agoAgree re the rounded corners. I think they were rounded before, but only two or three pixels maybe. Now with the greater rounding (which also forced them to increase padding to accommodate the rounding), it looks kind of cartoonish, rather than crisp and polished as before.
- t0astbread 6y agoA few months ago I think there were some fan-made "GitHub redesigns" floating around that sorta looked like this. It kinda reminds me of those crazy futuristic video game console "leak" videos (à la "This will be PlayStation in 2020!!") followed by the reveal of the actual new PlayStation design.
- amedvednikov 6y agoI think the old github design was perfect. Upcoming https://gitly.org https://gitly.org is going to have a similar design, even simpler. It's written in V, so it's very light and fast. Open source release this week. Other features (from the readme): - Minimal amount of RAM usage (works great on the cheapest $3.5 AWS Lightsail instance) - Easy to deploy (a single <1 MB binary that includes compiled templates) - Works without JavaScript - Detailed language stats for each directory - "Top files" feature to give an overview of the project https://github.com/vlang/gitly https://github.com/vlang/gitly
- ajoseps 6y agowhy is there so much dead space when you scroll down past the footer?
- gadrev 6y agoThey could use some alignment. It's one of the basic rules in design, and it really seems a bit off when the files are centered but the hmenu with Issues, PRs... is left-aligned. Maybe they had some cramming issues when there are many extra buttons in that row, since some only show up in certain cases, like the Settings button. Other things aren't so bad but I don't think they make up for breaking the general alignment in such an obvious way.
- 7ewis 6y agoI know obviously files are important in GitHub, but for the opening page of a random repo I think I would actually prefer to see the README first. I just went to the Explore page and picked the first repo: https://github.com/johannesboyne/gofakes3 https://github.com/johannesboyne/gofakes3 You have to scroll so far down to find out what the project _actually is_. I know there's an about message on the right, but it's not great. The new UI does look more modern, but there could definitely be some improvements.
- JoshTriplett 6y agoThat seems like a tradeoff between people discovering a project and people developing that project. People initially discovering a project usually want the README; people developing a project may potentially want either.
- 7ewis 6y agoThat is true, I don't really know what the answer is. You could do something like show half code/half readme, with extra code hidden behind a fold.. but I'm sure that would annoy devs working on those additional hidden files.
- JoshTriplett 6y agoI'd be happy with a README-first design that had a link to move the README below the code, and that remembered which one you want on top for each repository. (Along with a preference for logged-in users to decide what they want.)
- eeereerews 6y agoYou can also put a Readme in any folder and it will show up the same way. You usually wouldn't want those up top while browsing the files though. So it's also about consistency.
- njovin 6y agoI never look at the Code page of projects I work on. I'm always going straight to the pull requests or issues. I always thought the Code page's intended audience was new people checking out the repo for documentation or to peruse the code (usually after checking out the README).
- exochrono 6y agoI haven't had too much time to play around with it yet today, but Github is core to our development workflow and productivity workflow. Everything for our small team is tracked in GH issues and tagged with labels, and of course all our code goes through GH PRs. IMHO the features I use most (issues, pull requests, code browsing) didn't take any discovery to continue using normally and the interface was much faster, so I am a fan.
- rychco 6y agoI really wish the top half of the screen were centered (where the code, Issues, Pull Requests, etc buttons are).
- nshm 6y agoOne very important positive thing is that the whole readme is now displayed on mobile version and that is the one which is indexed by Google. Previously they only shown few top lines and thus all README was not visible in the search engine. Something that awesomeopensource took huge advantage of. I wish they can enable google analytics on Github pages.
- dvno42 6y agoLooks terrible. Figures MS would make it look FisherPrice like. GL it is.
- agustamir 6y agoOkay, is just me or does anybody else reduce the screen magnification by 10-20% when companies "refresh" their UIs?
- vaccarium 6y agoNot just you. I have to use Google search at 80% magnification tops, otherwise the results don't really fit on the screen.
- NuSkooler 6y agoThis feels like a huge step back. One of the first very obvious bits has been pointed out numerous times in this thread already: The main panel is shrunk down while various navigation is off in no-man's land.
- math0ne 6y agoThe number one thing I do on github is read README files and adding a right column just makes the area I use to do that smaller. The header thing must be a bug, I can't imagine that won't get fixed.
- dandep 6y agoI really can't look at a list of items without separating lines, i think it's a basic need.
- kapilvt 6y agonew ux sucks, on a wide screen content is no longer properly centered, horrible left float, right float on different elements of ux vs center box previously on core content elements. ie, it`s a bug not a feature.
- matterhorn2000 6y agoContrary to everyone else I really like the new design. The metadata is placed to the right as it should have always been. The languages are in the sidebar and are visible without me remembering that typescript is somewhat dark blue. Also the new look is more modern and unlike most people here I am not afraid of change.
- thex10 6y ago> and unlike most people here I am not afraid of change Hear, hear! I like the new design too. It overwhelmed me at first (somehow it felt really 'big' to me), and I'm still getting used to it on a visual level, but I appreciate all the new bits of information that I can much more easily access now (mostly in the repo sidebar). I also appreciate that the new design doesn't actually change that much. Overall, it still feels like... GitHub.
- microcolonel 6y ago> ...unlike most people here I am not afraid of change Not every preference is a fear, except I guess the fear that a lot of people will now waste a lot more time learning things that used to be obvious at a glance. The tables are somehow less dense and less readable at the same time; the added line spacing should have helped with this, but overall it's worse. The controls are needlessly stretched across the entire width of the screen, which these days is most likely wide, so reading and moving your mouse between controls is inherently more laborious (it's also just ugly).
- notdang 6y agoDid you check it on mobile or desktop? I like the mobile version, however I dislike the desktop version with elements scattered all over the screen.
- pan69 6y agoOverall this design change doesn't matter to me. The only thing that really stands out and that annoys the hell out of me is the circular profile images. It looks completely out of place compared to all the other elements on screen, even their generated profile images don't fit in it correctly. It seems that this decision was made not from "add value" point of view but someone just really liked Instagram or the look of some other social network and shoehorned it in there.
- jomar 6y agoI dislike large swathes of the new repository view, and I also especially dislike the circular profile images. Fortunately it's easy to use a little custom CSS to revert them to square images, at least for now: https://gist.github.com/jmarshall/a880c93725ee727abb5447358292b314 https://gist.github.com/jmarshall/a880c93725ee727abb54473582...
- dawnerd 6y agoI'm not a fan of the repo being center contained, but the navigation being full width. Things don't line up like they should and it just looks weird. Otherwise no real complaints about it.
- verdverm 6y agoActually, I think I'll just do everything from the terminal from now on. Anyone familiar with a great CLI? (that is not by GitHub)
- jonathan-kosgei 6y agoIt feels designed for larger monitors.
- hartator 6y agoI don’t like it either. White spaces and margin added for the sake of clarity when it makes it less readable. No more strict centering anymore. Avatar being rounded makes them loss information.
- wnevets 6y agoI kinda dislike it. I was part of the beta earlier this month and I switched back.
- deleted 6y ago[deleted]
- dec0dedab0de 6y agoFullscreen on my large monitor it looks ridiculous. On my phone it seems ok, except firefox crashed at one point. Developer tools should really be desktop first, instead of mobile first. I always wonder why we all use bootstrap as our goto so the site works on mobile, but then twitter barely works on a mobile browser.
- andy_ppp 6y agoIt seems fine to me in that I'm using it and have barely noticed apart from I have to scroll a bit more. It always amazes me somehow everyone thinks of the same ideas at the same time. MacOS Big Sur feels very reminiscent of some of these changes...
- joelkesler 6y agoThe new layout of the repo screen is decent, but the new, overly-smooth UI components are too much of a departure from the previous, well-done UI components. The way the top tab/nav bar stretches across the screen, while the content is centered feels broken to me. https://twitter.com/joelkesler/status/1275557934290755584 https://twitter.com/joelkesler/status/1275557934290755584 (above) I mocked up what the repo screen could look like if it used Github's previous UI with the new layout (and fixed the fluid tab bar!)
- microcolonel 6y agoI guess the upshot of GitHub burning their design advantage is that I no longer have to justify that when using GitLab. As a relatively long-time GitLab user, my feedback every time they change the design (often for the worse, in the same way as GitHub has now done) has been “make it more like GitHub”. Now what do I point at? SourceHut? I guess it is SourceHut actually; I think it could use a bit more texture/skeumorph on things like tabs and buttons, but it is so clean, especially since it uses my default sans serif font (which is condensed). There's just so much to do right, see: https://qui.suis.je/drop/sourcehut.png https://qui.suis.je/drop/sourcehut.png
- feikname 6y agoI think it's way more responsive, which is good. Hoowever, the increased use of horizontal space makes it harder to read (imagine HN without the blank sides) and I believe the information density has been lost a notch way too much. All in all I think I prefer the previous design because to me information readability comes first. It actually becomes pretty decent if you zoom out to 80% in Firefox although the text becomes a tad too small. I believe making an extension to increase information density shouldn't be too hard.
- yogthos 6y agoIt feels like change for the sake of change to me. There doesn't appear to be any actual improvement in terms of UI or functionality as far as I can tell.
- stanislavb 6y agoI think it will open a lot of work to many people that are scraping Github :)
- withinboredom 6y agoWhy would people do this? https://repo.git https://repo.git and shallow clone...
- bergwerf 6y agoI like that GitHub is one of the few websites that kept roughly the same design for years. Design is something that gets familiar, and I believe it helps your brain when it is not changing all the time. I would like to see an explanation from GitHub's side as to why this change was needed.
- bconnorwhite 6y agoThis 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 design sucks and how 5 years ago was "the good old days." The new GitHub design is objectively better. The new MacOS 11 design is objectively better. "Low information density" means less clutter. You find the information that matters quicker. Changes to padding/visual separation/sizing/etc. all provide similar context to which information is important, and how items relate. "Flat design" isn't some trend, flat icons are just easier to quickly recognize, and look far more crisp. In both threads the degree of negativity is disappointing. Can we not have one or two positive comments on how crisp the new commit graph colors look, how nice the transparent pin dragging interface is, or how the action buttons are more prominent? Not to mention the entire code/README page. The flat rounded corner borders are very clean! If you really don't like the rounded borders, use wget
- mixologic 6y agoLow information density means "less clutter" for somebody new to the interface, but it means "many more steps" to provide all the information that a dense design allows for. So much design fails to take into account human expertise, and our ability to learn complex interfaces. They get the A/B treatment which optimizes for beginners, which always leans towards the simpler, easier design. This is why we'll never get a better spreadsheet design. In the hands of experts it's already perfect. If modern UI designers were responsible for building musical instruments, there would be a lot more kazoos and recorders, and a lot fewer cellos and bassoons.
- bconnorwhite 6y agoExcel today is still cleaner than Excel 2010, and Google Sheets easier to use than both. Most spreadsheet users simply don't need the extra functionality Excel provides, and the few users that do need this use the product enough to have memorized the keyboard shortcuts.
- est31 6y agoThe worst part for me is the rounded avatars (the other rounded stuff is okay). So many pictures on github weren't built for rounding. My own avatar is cut off as well. I hope they revert it, but if it sticks around for a while I guess I'll have to update my avatar.
- kn0where 6y agoThe old Github was honestly a terrible UI. Not responsive at all, making it awful on big and small screens. The information density feels the same to me; it was low before and it’s low now, but at least diffs fill my screen (though improved responsiveness is something they added within the last year tbf). Unlike Jira, shit loads without a horrible amount of pop-in, and I don’t really realize I’m using a SPA. They didn’t rearrange the core UI much, and I don’t feel like I’m having to relearn anything. So overall, some ambiguous buttons are my only complaint. Feels like a big improvement that was long overdue.
- markstos 6y agoCouldn't easily find the "releases" page.
- markstos 6y agoSearching for an issue was disorienting.
- mcintyre1994 6y agoNot sure if it’s part of the new design or just a feature I haven’t seen before, but converting links to a line of code into a code view displaying that code in issues is great.
- MH15 6y agoThe only problem I have with the design is the repo header not being centered. I'll fix this with some userstyle CSS but it's a terrible design pattern. Other then that I actually really like how it looks/feels/works.
- deleted 6y ago[deleted]
- kylebarron 6y agoIs there any way to revert the changes?
- systemvoltage 6y agoLoss of borders in the tables (source code file tree).
- bE9a3S5So8igd3 6y agoThe worst redesign yet. It looks even worse than an early version of Gogs I tried. Of course, if you're paying designers they ultimately have to design something even if it's crap. Ideal github design was maybe in 2012. Unrelated to the redesign, but the documentation for things like Actions just scream "microsoft." It was really hard for me to find the important information; had to sift through pages of abstraction gunk where things aren't explained clearly or with code. Felt like IBM product pages. Very non-github. This clueless internet-explorer-type design trend will almost certainly continue IMO. They simply can't help theirselves. Unfortunately I also don't like gitlab or bitbucket. Github circa 2012 was the gold standard for the design solution, while everything else was cluttered or pad-y or overreliant on side navigation. Now everything sucks. What's sad? Actually, you can find the classic (good) github design alive and well in China: https://gitee.com/drinkjava2/frog https://gitee.com/drinkjava2/frog
- GuiA 6y agoSorry tangential, but what's this frog neural network project? Looks fun!
- bE9a3S5So8igd3 6y agoOh, I dunno I just found that by exploring gitee
- ulisesrmzroche 6y agoIt’s a good redesign. Not great but that’s ok. What we need to talk about is the quality of the criticism. It on par with the “why would anyone use Dropbox when rsync exists” People hate websites that look like they were designed by a programmer. Programmers hate websites that look like they were designed by a programmer
- charlesdaniels 6y agoI don't much care for it. It seems to make much less efficient use of screen real-estate. Information that used to be clustered tightly together is now spread all over. It seems to me like someone who doesn't actually use git professionally just arbitrarily move things around for no discernible reason. The UI elements that have moved don't seem to have any particular rhyme or reason. For example, apparently the "security" tab is worth being in the tab bar, but the releases aren't? Frankly, I think it's inappropriate for a professional tool to change it's UI arbitrarily, or even for a marginal benefit, since all of the great many existing users now have to learn the new UI. These things should only be modified if there is a clear and significant benefit that justifies the trouble. This makes me glad that I'm a Sourcehut user ( https://sr.ht/ https://sr.ht/ ), since it's UI is much more sensible, and faster to boot.
- superasn 6y agoIt's a disaster. I was so happy that i could just turn it off but now they have removed that option. Reddit really has done a great service keeping old.reddit.com, wish gh did too.
- cgreerrun 6y agoI wish the code panel was collapsed by default on the repo home page, so that you could see the README section front and center. That's usually the first thing I read. Then I dive into one or two files to check things out.
- LegitGandalf 6y agoIs there a way to use the older interface, kinda like old.reddit.com?
- ddevault 6y agoDisclaimer: Founder of a GitHub competitor here I use GitHub very little these days, and have mostly removed it from my daily workflow. But, on the whole, I mostly like the new design. It's more pleasing to look at, and doesn't really interfere with the things I still come to GitHub to do. I still feel that the notifications redesign was poorly done, however, and that's where I spend most of my time. I ended up completely disabling almost all of my GitHub notifications as a result. The notifications redesign drove me from visiting GitHub a a few times per day to a couple of times per week. But to be honest, my usage was already on the wane by then, it may have just accellerated it.
- foresto 6y agoUgh. Yet another design by someone who keeps their browser window maximized (or has the luxury of an enormous display) and expects everyone else to do the same. A few things that leap out at me: - Large margins everywhere - Sidebar gobbling up 20-30% of my browser window's horizontal space, no matter how far down I scroll. - Hamburger menu hiding the dashboard and other frequently used links. - Latest commit timestamp hidden by mostly useless stuff like tag and branch count. This layout wastes a ton of space. Information density feels too low, which might be appropriate for a product landing page, but is counterproductive in a development tool. It also makes things needlessly difficult for people who multitask with side-by-side windows or have small screens. On the positive side, at least this layout is less annoying than Gitlab's "bury everything within javascript menus" approach?
- realusername 6y agoI have the same complaints, I do agree that the new redesign looks great in my external monitor, except I do my browsing on my 14" display and the repo information looks kind of squished into the left.
- coronadisaster 6y agomaybe they should accept pull requests
- prputnam 6y agoIn a quick browse of the thread I didn't see this mentioned yet - it seems to have broken multi-line suggestions which I thought was a great addition. I do wish there was an option to use more screen-width, and this does seem to be a step in that direction.
- gsich 6y agoClone URL should be visible instantly, not after 1 click. It's by far the most common thing I need.
- arriu 6y agoToo many rounded corners for my taste. Functionaly, I'm having trouble finding things. Half of it is just because it's new but honestly some of it is due to stretching information apart.
- adventured 6y agoThe last version of GitHub had as many rounded corners. They didn't change that, they increased the roundness (they increased the border-radius).
- dilap 6y agoYeah, it's bullshit. I think once a company gets "big" and corporate enough, focus somehow dissipates away from actual usability into...something else. See also: all recent changes to Slack. Maybe this is just because the best people are drawn to work on new products? Another insane example of this is scrolling in the iOS AppStore app. If your finger happens to start a scroll on a button, the scroll is just completely ignored. Apple used to write entire carefully-considered tech reports about how to handle this case (until the finger starts to move or some time has passed w/o moving, you're in a limbo state where a button tap or scroll can't be distinguished), but now they don't even try to get it right.
- Thorentis 6y agoSince the repo screen is now basically full width, why not add a simple commit stream on the left? (So make it three columns instead of two). The most important thing I look for when checking out a repo, is how much commit activity there is and what sort of things are being worked on. It gives you a good sense of the health of the project. So in the middle you have the files, and the action buttons above that, on the right you have info on langs, the contributors, the "About" blurb, but on the left you could put a (live updating?) commit stream with just a small contributor pic and name, hash, time stamp (x days ago), and the first bit of the commit message. EDIT: Instead of just a commit stream, why not add a "repo feed" on the left? Includes new issues, PRs, commits, etc. Live updates (animates new ones bumping into the top).
- talideon 6y agoIn aggregate, I neither like it nor hate it. But here's what I hate: * It's even flatter than the previous layout, which makes it more difficult to use. In particular, it's easy to miss the branch dropdown. * It no longer shows the last commit message, which is an extremely useful thing to be able to see, as others have noted. If space is an issue, they should shift the junk on the right of that section up beside the 'branches' dropdown.
- forgotmypw17 6y agoThe previous version required JS to view list of commits. New version displays them all. Thank you.
- jes5199 6y agoI think the icons are a little less legible. Not a lot, but just enough to wonder if I've screwed up my browser's zoom level whenever I see them
- yellowapple 6y agoI do like that the page does a better job of filling the window; nothing irks me more than wasted space. I also like that it's a lot friendlier to narrow windows (no horizontal overflow/scrolling); makes it more convenient to put it side-by-side with something else.
- GuiA 6y agoI'm surprised I'm not seeing more people talk about source hut (https://sr.ht https://sr.ht) on HN. If you're a github/gitlab/git* user it does all the things you want, has a lightweight text focused interface, it's run sustainably, que demande le peuple. I am not affiliated with Source Hut in anyway other than being a satisfied customer.
- montalbano 6y agoIt's all fine for me except: main repository view on widescreen puts all the "Code, Issues, Pull Requests etc..." buttons way over to the left. Why not just centre it like the repository files view below it? Seems completely bizarre and adds extra mouse movement between files and the buttons above.
- jp_sc 6y agoI love it! It is finally usable on mobile.
- winrid 6y agoI really don't like seeing the code stats way at the bottom. Also, on mobile I'm not really sure how to go directly to commits to master. Edit: figured it out...
- etimberg 6y agoWith the new notification layout, I lose a lot of vertical screen real estate on a laptop. Between the site header, the repo header, and the notification bar I probably lose 50% of my screen.
- steve_adams_86 6y agoIs it normal to ship with scss source maps? It seems like it would be a net negative for performance and delivery times.
- arshbot 6y agoSome positive feedback that may be overlooked with all the UI changes: Love that releases are shown prominently on the repo page! It's always been a 'trick' of mine to check for releases for a repo by appending `/releases/` to the URL. Now I don't have to, and can just peek at a glance.
- bewestphal 6y agoI’m open to change. But I question whether this was necessary. I’ve admired Github for having a clear and readable UI that didn’t change. All their UI feature additions before I thought were fantastic. Devs don’t want to have learn new things if not necessary. I’m hoping it will grow on me.
- CGamesPlay 6y agoMy browser window is 1059x751 (inner dimensions; to get yours, open your web inspector and type window.innerWidth). For context, this is a desktop machine, but those dimensions fall into Bootstrap's "tablet" size. The only thing I immediately noticed is that README's on the project root have lots of wasted space to their right. Interestingly, historical versions of Github seem to go back and forth on this (the presence of a sidebar) every major redesign. > Migrating to gitlab... Wow, some serious "looks like JIRA" PTSD there. Did Gitlab promise they wouldn't redesign?
- dzonga 6y agoit 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.
- keyle 6y agoI 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...
- peterwwillis 6y agoImagine 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.
- meddlepal 6y agoI 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.
- csande17 6y agoOne how'd-they-ship-this regression is the weird double focus ring that appears when you click the search bar on https://gist.github.com/discover https://gist.github.com/discover .
- kanglelin 6y agoI think it was much cleaner, does anyone hate it actually?
- pryelluw 6y agoIts basically JIRA. Hate it. Hoping they let users opt in to use the older UI.
- miguelmota 6y agoNever liked how Microsoft designed things because it feels unfinished and contrast of colors is bad. Certain content is pushed to the edges of the screen for no good reason and some of the fonts are a light in color making it hard to read. The commits link is not obvious anymore that it's clickable. The redesign is not that bad but there's still a lot to improve on. Before it was easier to scan the page from top to bottom but now the page feels a lot more busier because there's more dropdowns and sidebars. I feel like my eyes are jumping all over the place trying to locate things now. Wish they had chosen functionality over design.
- sixers2329 6y agoThe releases on the sidebar is handy, but something about the top of the page feels... disconnected. I think I’d like the “about” section at the top rather than in the sidebar. Getting rid of the double nav is a good improvement. The non-centered readme is a little triggering, but maybe I just need to get used to it
- cocoa19 6y agoI don't like it compared to the previous layout. The new layout has soft boundaries between boxes that make it harder mentally to distinguish one box from another.
- opqpo 6y agoIt's worse but still possible to swallow for me.
- alexmingoia 6y agoNothing has been improved, only changed for the sake of change. A redesign without a user requirement or business concern indicates mismanagement. If designers or management wanted a new look they should have coupled it with functional interface improvements. Changing the style alone has a lot more potential downside than upside. And of course in the quest to re-skin everything for no reason, important things like last commit message and status were removed.
- alappin 6y agoI don't mind the new look and feel. They made it look a bit more polished.
- Seb-C 6y agoI mostly don't mind (like 99% of redesign these days, it is pointless), but the new one makes many things harder to read: - I don't know which menu or tab is selected (the tiny border is not obvious enough) - The buttons don't have a state anymore, so figuring out if I am following this repository or not is difficult - The file browser does not have a clear separation (border) for each file, nor does it have alternating background colors. That makes the navigation harder. - I am disappointed to see that the redesign did not get rid of the useless in-page loader when I click on a link. This is annoying and breaks my normal navigation.
- flaque 6y agoPersonally, I love that it fits perfectly in exactly half of a 15-inch Macbook Pro screen. That's always how I have GitHub open and it bugged me that it didn't fit right before.
- deleted 6y ago[deleted]
- Retr0spectrum 6y agoI'm pretty change-averse, so I tend to navigate sites like GitHhub by memorising URL paths of pages I frequently use. For example, I have /commits and /releases memorized. This makes it much easier for me to adjust to weird design changes.
- abathur 6y agoI got the option to opt into this "feature" a few (4? 5?) days ago. I've been intending to give feedback, but haven't had time, yet, to take screenshots and marshal my thoughts. I don't want to over-perform it, but I'm annoyed GH bothered prompting me for feedback on something that they were going to general release in less than a week anyways. I'm not really a cranky person, but I already wasted an hour of my life looking for some good plugins that would help me annotate the page to illustrate my thoughts. I have a billion things more important than giving GH free feedback on my plate, but I was nonetheless naively looking forward to giving feedback on it because it was the first time I've ever been opted into a UI experiment where the ability to give feedback was so prominent that I felt like anyone actually gave a shit. So. Now, I'm cranky. 1. The visual alignment of this design is miserable relative to the previous. I'm willing to entertain counterpoints from the actual designers here (and I do appreciate that this design is more responsive). I was going to send a number of nice little graphics illustrating how multiple strong visual lines are destroyed by this layout, but I'm not frittering away any more of my life on it, now. 2. The list of releases is probably the single most important signal on the page. And now, if a project has no releases, it's just an absence. There's no indication. I just have to know, from its absence, that there are no releases. 3. It's covered elsewhere in the thread, but I agree on the languages being moved. Someone notes that the existing location was obscure; fine, just force the existing indicators to expanded-by-default. They were in the right place. The second most important signal is what languages a project is in. In some responsive views this information is now at the bottom of the page. This is absolutely backwards. Everything else on my commentary list is probably covered elsewhere here. If not, I don't really care. P.S. In the future, don't jerk people around with feature opt-ins with less than a week of turnaround on feedback.
- echeese 6y agoIt'll take me a few days to get used to it but it's not bad.
- deleted 6y ago[deleted]
- carapace 6y agoIt seems faster. Quite snappy.
- peterkos 6y agoAside 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.
- baby 6y agoI like it!
- deleted 6y ago[deleted]
- systematical 6y agoI don't like it. They pulled a reddit and their UI was already WAY better than old reddit. I don't mind the side nav though.
- mariocesar 6y agoThe code is not in the center, is not the main thing, they are pushing me to read the sidebar with actually no useful or inmediate information I need.
- DeepYogurt 6y agoWhatever
- pcj-github 6y agoI feel like they are setting up a design iteration pathway to making changes that will ultimately make it look more like vscode. Seems like a MSFT influenced-thing. Don't love it.
- perryizgr8 6y agoI am no UI expert so I will not try to evaluate the old vs new UI. However, I want to say that I really like the way Github has looked and functioned. It feel lightweight and it feels like someone just built it up from basic html. For example, you can right click the "go to file" button and open it in a new tab and it works like any standard link. Compare that to any button on facebook or youtube or gmail which are probably not even real html buttons, you can't expect them to properly open in a new tab.
- RNCTX 6y agoIt's bad. The only way they could do such a thing and not drive people away would be to come up with more useful features, but their redesign seems to have less basic functionality than the old UI did. Microsoft will understand that github users don't care about their "branding" and if they don't, they'll simply drive those billions of dollars into an early grave like Yahoo does with everything that Yahoo buys.
- michaelangerman 6y ago>> They've added a right-sidebar that shows various info about the repo in general, like what the last release is. How do I get rid of the right-sidebar ? This is terrible and a complete waste of real estate. And hopefully someone will tell me how to get rid of it... Thank you !
- toohotatopic 6y agoWith proper MVC design, why can't they make a new design optional or at least make the old design accessible like old.github.com?
- sandGorgon 6y agoit deprioritises the readme. which was the whole point of Github.
- lukasdanin 6y agoMy only suggestion in to move the Sidebar to the left when viewing a repository's files/commits, or at least give us the option to do so, which is easily doable by injecting custom CSSs into the page using Stylus btw. Everything looks great so far, so kudos for everyone involved.
- villgax 6y agoNeeded Dark Mode as well
- anonfunction 6y agoI don't mind the aesthetic design changes but the layout drives me crazy. I count 4 separate alignments in the new repo page on my 15" macbook's full width browser window! I found and modified a Firefox user style to fix the alignment for wide windows. Original mozilla userstyle: https://gist.github.com/healingbrew/acc65ad439379eabdbb276e86975275e https://gist.github.com/healingbrew/acc65ad439379eabdbb276e8... Modified stylish chrome extenstion userstyle: https://gist.github.com/montanaflynn/ca64cc0fcf55bcd4556a016bffd8a7e3 https://gist.github.com/montanaflynn/ca64cc0fcf55bcd4556a016... I use this regex so it doesn't apply on the full width logged in homepage or /notifications: https:\/\/github\.com/(?!notifications)(.+) Here are some screenshots. Before: https://imgur.com/3ogzYhI https://imgur.com/3ogzYhI After: https://imgur.com/8zMwTLL https://imgur.com/8zMwTLL
- amarshall 6y agoThank you for this, using it now.
- darepublic 6y agoI don't like the clone button is now a big ugly pill button. I will probably get used to it, but damn you github UX designers, fixing what ain't fucking broke. You should use your fucking creative brains for real problems, PLEASE!!!
- ciguy 6y agoOthers 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.
- some_developer 6y agoEverything 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.
- justcontent 6y agoLess is more.
- redisman 6y agoWell 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.
- Quelklef 6y agoYeah. I think that the new layout is fine, but I really don't like that it doesn't look like GitHub anymore. It looks like every other modern UI out there.
- snissn 6y ago1) it lists "contributors" in the corner and listed an old employee which made me worry that they were still able to access the repository. they're not. i don't need to see their profile on my repo, it's not helpful 2) because of that I noticed that i'd been paying for two additional seats for god knows how long and downgraded. I'm kind of disappointed i've been overbilled for no reason
- tregsthedev 6y agoI love it, Makes me feel rly nice. If you want to move to gitlab, That's your call. But this new designhas really made me want to use github more. Github Feels more Natrul to me and I finding that enjoyable
- smabie 6y agoI really like it. Looks really good. It's possible that they could put more information on one screen, but I'm sure they'll iterate and add some tweaks.
- surajs 6y agoit hurts my soul....why Microsoft? why must everything look like it's a corporate sellout?
- quickthrower2 6y agoI'm used to Jira changing their interface more often than my socks get holes in them. So this is small potato and my well trained UX boobytrap avoiding subconscious navigated it beautifully.
- h3ll0k4ll3 6y agoThe 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 cute / nice enough for actions. So they re-designed the entire site to be able to push us towards Azure usage. ( that is the entire reason Microsoft Acquired github - slowly luring developers from opensource to the safe walled garded of microsoft. With a slow shift of Azure cloud offerings leaking in to our minds. ). And slowly taking over most organisations tool-chains.
- brian-armstrong 6y agoWhat is an action? And is there really much risk of us using Azure? My code, like most I suspect, runs on linux/unixy things and probably doesn't even build on Windows.
- gnur 6y agoI'm pretty sure I read somewhere that at least 50% of the vms running in Azure are actually running linux. And in this case, "action" refers to the ci/cd tooling github provides called "github actions". It's one of the tabs at the top.
- h3ll0k4ll3 6y agoThe risk is determined by us the developers. Actions means "Github Actions - re-branded Microsoft ci/cd tools). Microsoft uses partners to sell their offerings. Many of these have used cross-selling with the arguments of all eggs in the same basket and buying from one vendor "more secure and safe" for decades. Tools like Github and Some of the best and most creative developers not using Visual Studio threatened this method of selling. (the IDE runs and deploys "solutions" to Azure directly - very effective walled garden ). The free thinking and creative developers had started to break organisations free from the microsoft "safe basket" and the push towards AWS and GCP was hurtful to the bottom line. To counter this a strategy was formulated. Microsoft rebranded as the good guys. With an image of participating and actively supporting opensource. First they tried with pushing .NETcore. Then they gave us VS Code. Then they aquired Github. And now the cross-selling is back in the game. The arguments of "one vendor" and "one basket" is thrown in your face again - when dealing with procurement people and internal organisation politics. "We argue Microsoft as the better option here - we in procurement have a good relationship with Partner X who have helped us with Office365 for years". "They told us you already have The Github from Microsoft. And our Code already lives in Azure. You in IT really need to motivate why a different vendor is required for all this cloud stuff". And the herd of sheeps are slowly returning to the garden.
- arrayjumper 6y agoUsing 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.
- Quelklef 6y agoYou can use Stylish [0] to write custom per-site CSS! [0] https://chrome.google.com/webstore/detail/stylish-custom-themes-for/fjnbnpbmkenffdnngjfgmeleoegfcffe https://chrome.google.com/webstore/detail/stylish-custom-the...
- lizerome 6y ago>the buttons in the header are separated to the extreme ends of the screen >...but the elements in the global site header aren't (for some reason) >the selected tab has a thin underline which is harder to recognize than a colored background, and isn't as clear (does it mean I'm currently hovering over it, does it just mean that section is important, is it the same as a notification badge, etc) >the main column is off-center >there's no separation or contrast between the list elements, making it harder to align things by eye >the readme section doesn't have a header, making it look like the text "README" is part of the document itself >there's an entire second column in the layout, placing both on an equal level of importance >...but it only has a single paragraph in it, which leaves you with an empty column taking up space 95% of the time >if a project doesn't have something, the sidebar will simply omit that section instead of showing the same element with the text "0 releases", "0 branches", etc. >...which in turn trains you to ignore the contents of that column and not expect to find things there >this also applies to the "about" text, the purpose of which is literally to be the first thing you see when loading the page - now in the sidebar, sandwiched between three lines of text in the same font, color, weight and length >the labels at the bottom of the page are spaced out evenly, which actually makes them feel HARDER to click (the sizes of the hitboxes are the same, they're just much further apart) in addition to looking ridiculous Guys, stop complaining. You're just afraid of change.
- greggman3 6y agoWhat 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 https://github.com/username/reponame/code or the links to various branches would suffice for me. Even if I am looking for the code the 95% of the time the code is not above the fold, instead there are several lines of folders and config I don't care about and so I still have to scroll down or search. In other words, the code at the top doesn't even help for code. To put it another way, the code at the top is actively hostile to what I need to get done.
- laumars 6y agoBitBucket follows this principle and it’s one of the main reasons I hate using BitBucket. The vast majority of the time I arrive at a git repository is because I want the source.
- greggman3 6y agoBy "want the source" you mean you want to look at the source via the gitlab website ? I would interpret "want the source" as "I want to download the source" in which case showing the files is useless. All you need is a "download source" button
- laumars 6y agoThe conversation was about viewing the source online vs the README so clearly I meant I want to glance through the source online. There's a few reasons I might be doing this: - before deciding if I want to clone the repository. - Or sometimes I might just want to check the hooks of a particular API (eg the outputs of a Terraform module) where there isn't really a need to manually clone the repository just to validate some assumptions. - Sometimes I might want to quickly verify the code that's on origin master is up-to-date (everyone has committed PRs and merged back into master). - Sometimes I might just want to validate what code kicked off the CI/CD pipeline. - Sometimes I might be demoing some changes in the sprint review and rather than spin up another IDE / switch branches / etc I might just open a new tab and walk the team through what has been committed on Github Also nobody was talking about Gitlab specifically. BitBucket and GitHub were mentioned though.
- noway421 6y agoI love it, just miss the percentage breakdown of languages on repo page.
- rezonant 6y agoMy biggest problem is the Find File feature no longer shows up on mobile... This is a super handy feature for mobile specifically. Hopefully they'll put it back.
- jlarocco 6y agoI think it's great. It's about time they started using more of the available screen space. If I want a tiny view I'll shrink the window. Since 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?
- hackerman123469 6y agoMy opinion is that Github now looks like a default bootstrap theme.
- beshrkayali 6y agoOn a 3840x2160 res it looks horrible, extremely stretched and honestly it looks like someone's first web design, and if you zoom in it looks unbalanced. There's no reason for the major layout change. Sadly, this seems like yet another case of designers/project-managers having nothing to do and wanting to feel useful every once in a while so they go about redoing the design. Paypal, slack, spotify, and many others do it all the time it, so why not github.
- tinix 6y agohate it.
- hivacruz 6y agoI really don't like the sidebar on repo view.
- Insanity 6y agoI think it's fine really. I wouldn't say it's an improvement over the previous version, but it's not worse either. Took a bit getting used to, but I can still find my way around the repo.
- VariantXYZ 6y agoThe commit message not being shown anymore and the CI status badges not showing up kinda suck. Otherwise, as a repo maintainer I don't really see much other benefit. As a user, I do appreciate releases being just... there on the front page. That's really about it though. Everything else sorta just feels the same. Also, I don't mind using the right side for more information but... can we just left-justify the whole page instead of centering it? It'd provide way more space for info on the right and wouldn't... just be completely empty on the left.
- tuananh 6y agoit's bad. - information is scatter everywhere - release is a lot hard to find - UX is bad on wide screen. I use a 32:9 49" monitor and it's pretty bad.
- heipei 6y agoUgh, just realised how bad it is. The menu bar and repo toolbar are float left/right but the repo content is in a centered max-width div which means that it does not align with the buttons and text in the bars above it at all. Who the hell came up with that design, it's unusable!
- jmiskovic 6y agoA related question: Why is it so hard to find a most up-to-date fork? When I come upon a useful lib, there would often be hundreds of forks. 99% of those forks don't make any commit on top of upstream repo. Why even bother forking if you're not actually changing the code? Can we agree those are useless and just hide them in GitHub interface? You can list all the forks on GitHub, there's even a nice hierarchy, but no other information. So you open hundred tabs and scan all the forks to see if they are ahead or behind the original. There must be a better way! Few years back there was a graph that took forever to load, but it gave good idea of commits that each fork applied on top of original. Is it still available?
- jmiskovic 6y agoIt seems fork graph as a feature is now available only to GitHub Pro / Teams accounts.
- ethanwillis 6y agofile size? I have to click a bunch of files to see if they're even viewable. E.G. which of these files are data files small enough to view and which are not? https://github.com/LahiruJayasinghe/RUL-Net/tree/master/CMAPSSData https://github.com/LahiruJayasinghe/RUL-Net/tree/master/CMAP...
- ilmiont 6y agoLooks horrific at 3440x1440...
- FZambia 6y agoI also don't really like new design of main repo page. Repo short description on the right – so inconvenient. BTW this is how it looks on mobile: https://i.imgur.com/SqV23WN.jpg https://i.imgur.com/SqV23WN.jpg - the most interesting things about repo usually located in first lines of README - now we can't see it.
- janpot 6y agoI often go to a repo and look at the recent commit history. Maybe it was just muscle memory, but I keep struggling finding where to click for this, especially on mobile. Doing this now takes me considerably more time with the new design. (been on this for a week or so)
- LukaD 6y agoThe new layout is so bad I no longer click on Github links...
- merb 6y agoI think it's really strange that they redesigned it, but still do not have settings to use the full width...
- battery423 6y agoI'm not sure why you would get rid of the table lines. Like "hey lets get rid of the eye guidance thingy, so it looks less like a table?!"
- greatgib 6y agoFor me it is a bad and unnecessary rework. Exactly the kind where they break a functional design that was refined for multiple years. And they break it just for a product management/ marketing reason to have 'something new'. Both on desktop and mobile there are a lot of useful info lost and at the same time, low density and a lot of empty space. But in addition there is no coherence. For me, the mobile experience is illustrative. Look at the screenshot examples there: https://twitter.com/greatgib42/status/1275703359283122183?s=09 https://twitter.com/greatgib42/status/1275703359283122183?s=... If you had no knowledge, you could think that after was in fact before. Issues that I can see: - No part of the readme/description visible anymore. - Stupidly lost space, like nothing anymore in the top bar to use additional line. - stars count was smart before by being on the button itself. Now one big empty button and a separate counter. - for commit, issues, project... Everything was directly visible before. Now, a horizontal scroll is needed. I hate having to horizontally scroll on mobile web. (But maybe it is just me)
- greatgib 6y agoFor a fun test, I showed my GF the 2 screenshots. I tried to avoid involuntary giving any clue, and asked her which one, she was thinking was the old interface and the new one. She is not a geek, not in tech, and does not know Github. But, you can bet it, her guess was that the NEW interface was the oldest one, and that the OLD one was the recent rework... That is an interesting test to rule out the fact that we are "adverse" to changes.
- playpause 6y agoI'm not sure why that rules out the idea that people are averse to design changes. For one thing, it's just one piece of anecdata. For another, just because someone thinks Design A looks newer doesn't mean that they wouldn't prefer to keep using Design B if they were already used to it. Anyway, even if we accept that people are generally averse to changes, that doesn't imply that all criticism of a redesign should be dismissed as aversion to change.
- livealife 6y agoSucks. Migrating to BitBucket.
- battery423 6y agoThey are able to completly redesign the layout but adding a TOC feature to their Markdown, no way. Please add a TOC Feature! Use what you have with github pages and Markdown!
- heavyset_go 6y agoI really dislike circular borders on profile pictures and can't wait for this trend to die.
- wiredfool 6y agoScrolling feels jankier on large syntax highlighted pages. The livesearch loses focus, then selects the whole item if you pause for a second. If you then continue, the search is borked. If you search fo something in an organization, the next time you try to search it searches the whole site.
- rcshubhadeep 6y agoI hate it! Simple
- aogl 6y agoI don't like it and it reminds me of Bitbucket :(
- adadahdjej 6y agoI honestly hate the design with the fire of a thousand suns. The navigation aligned on the left and the main section with code centered is so unbalanced it makes me nauseous.
- brainzap 6y agoI think "Release" deserves to be in the tab, I use that feature a lot. For example Microsoft uses it heavy to provide changelogs to users.
- tenryuu 6y agoMade my own userstyle to alter it all. I removed a lot of the rounded corners on pretty much everything. They're still round (2px perhaps), but not as dramatic as they are being served. Only problem is that I didn't save the damn thing before my browser crashed. And critically, made avatars square again
- dwarfstarlinux 6y agoIt does not feel like GotHub anymore. The old layout always had a more robust feel. Now it is too modern. The main thing that bugs me is that the languages of the repository are at the bottom right now instead of the top.
- asjfj9 6y agoWhy fix something that's not broken?
- udkl 6y agoA relevant discussion from 2019 https://news.ycombinator.com/item?id=19276113 https://news.ycombinator.com/item?id=19276113
- switch007 6y agoI took an instant disliking to it. My eyes hurt. Some vertical alignment is off. I dislike the wide layout. Was there a reason other than "it's 5 years old"?
- moltar 6y agoIt’s ok, I’ll get used to it.
- righteous 6y agoDamnit GitHub. Why mess with perfection? Also, does nobody on their design team use an ultra wide monitor? Why break the container on the navbar? Now I have to love the cursor for what feels like forever to change repos.
- hoss_pumpkin 6y agoIt looks kinda (being liberal here) like the old theme, but slightly worse and it has issues: 1.) Everything feels left especially on my 21:9 display. This makes going from opening issues to clicking "Code" a very long mouse movement. 2.) There aren't grid lines on the file view. 3.) It looks unprofessional. Professional tools have this feel to them, and this new theme doesn't have it. It feels like a toy that shouldn't be in the toolbox. At this point I may just move to GitLab. It seems more feature packed and you can have it mirror a repo to GitHub for the users don't want to make the switch.
- k0dede 6y agoI must be lazy. I don’t want my eyesight travel from left to right in like 100ms. It should be like notepad, open it up and resize it whatever you want.
- parasanti 6y agoI think it is horrible. I feel it's harder to read overall and harder to navigate. I am of the feeling, if it's not broken.....
- RocketSyntax 6y agoNeeds dark mode
- codywan1996 6y agothe column on the right takes whole lot of space from README. It just looks very annoyingly un-balanced.
- codywan1996 6y agothe column on the right takes whole lot of space from README, which looks annoyingly mis-aligned.
- jedwards1211 6y agoMy first thought was good ol' Microsoft UX design... Wish they had kept the description and page URL top and center. And at least made the tabs and badges area the same width as the content. I bet they'll eventually come to their senses about that.
- wallstprog 6y agoWhat happened to "forked from"?
- antpls 6y agoI don't have repo on GitHub, but the mobile version is better for me so far. It uses all the screen space, and now we can finally see the language bar (% of languages used in the repo) on mobile version, which wasn't possible before.
- retorquere 6y agoIt's fugly. I thought a plugin broke rendering on GH. This seems like a change for change's sake -- I don't see what this was supposed to accomplish. Put back the "releases" link where it belongs for a start. And why is the code-issues-pullrequest etc left-aligned and the content it governs centered? How did this get out the door?
- makecheck 6y agoThey need to get rid of the “sign up for GitHub” thing, which is especially egregious on mobile where it’s half of the initial screen. I hate having to scroll just to see things. I’d imagine 99% of visitors are on GitHub but, like me, are not always logged in and I’m not going to when checking simple things.
- deleted 6y ago[deleted]
- Emyjamalian 6y agoThis new design is so smooth and friendly though. I mean, it's Github, not a social media.
- maxwroc 6y agoThe header sucks on the ultra-wide monitors as you have one set of the buttons on the left side and other on the right while the main content is in the middle. It completely destroys typical page parsing habits.
- NoKnowledge 6y agoIt's broken for me, thanks to the "responsive" design. When the browser window occupies half my screen (1920x1080px), the top-right menus (bell, plus, profile) get replaced with only a bell icon. How am I supposed to reach the settings page now?
- sraw333 6y agoI really hope they can revert this, it is really ugly.
- sraw333 6y agoI really hope they can revert this, as it is too ugly.
- stockkid 6y agoPersonally I have noticed some changes, but nothing that impacted my productivity in any significant way, and paid no more attention. I believe sometimes we tend to overreact to certain changes that have minimal impact on our lives, because of our attachments to the tools. For instance, on HN, we seem to get a sea of "That's it I'm moving to Firefox/GitLab/etc.." comments often when their counterparts change something. Sometimes those reactions seem warranted, and in this case, not really.
- Ardefactual 6y agoWhy would I want to be able to see a bunch of meaningless icons for contributors? Why is this being prioritized in one of the highest visual-traffic sections of the layout? Why would I want to see what percentage of the project is in different languages as a high priority piece of information? Like, 100% agreement with everyone complaining about how the sidebar de-centers the README, agreed, that's awful, but what rubs salt into the wound is the sidebar is full of useless garbage! Both as a contributor of code and as a consumer it's hard to imagine things I'd care about less. Have it in a cute little "info" tab that no one will ever click like all useless information, and keep the landing page of a project for essential information.
- nazerimahdi2001 6y agoSeems very solid to me.
- perpetualgrimac 6y agoA friend of mine dislikes the redesign due to (a) the sidebar taking up too much space and (b) the lack of gridlines in the file listing. Here's some CSS that addresses those issues in case anyone else wants to blast it in via browser extension: .repository-content > .d-flex { flex-direction: column !important; } .repository-content > .d-flex > * { width: 100% !important; padding-left: 0 !important; padding-right: 0 !important; } .repository-content > .d-flex > :last-child { margin-top: 2rem !important; } .Box-row:not(:last-child) { border-bottom: 1px solid #e1e4e8 !important; }
- sbr464 6y agoI also found that it took a while to find the commits page. Not GitHub web related, but on the mobile app, 2 issues I've came across: 1. Not being able to click to a repo home page if you are on a nested page, or link to a file from the web etc. 2. Markdown files displaying in raw form when someone links to a ReadMe.md file directly etc.
- jacke127 6y agoTable view of files looks terrible. Hope they will fix it
- peternicky 6y agoI tried the new layout when offered as a beta feature and very quickly realized it was a regression in terms of ease of access to the information I want when I navigate to a repo page. I’ve submitted multiple feedback messages and was shocked when this was pushed through. Natfriedman, please consider these points.
- lukyvj 6y agoIt's terrible.. Please, let us go back to the previous design..