8 ms·
Thanks for the feedback about the latest commit status. This is something we should definitely fix. Also – I don't think there is a principle of lowering infor
by natfriedman 6y ago
Thanks for the feedback about the latest commit status. This is something we should definitely fix.
Also – I don't think there is a principle of lowering information density at work here. I think it's just a design that we will keep iterating. We are pro information density at GitHub.
- chrisandchips 6y agoIt's great to read this comment - it's always nice to know that community suggestions aren't just cast into the void
- nmstoker 6y agoYes, I was really impressed to be contacted by a genuine developer with sensible questions when I gave feedback on the GitHub Android app beta a little while back (funnily enough, given other comments here, my concern was it had simplified away something I found useful!)
- baby 6y agoReminds me of when HN added the [-] and everybody complained it was on the wrong side but they couldn’t be * to fix it.
- zacharycohn 6y agoI love that it's on the right. It means when on mobile, I don't accidentally upvote something that I meant to collapse.
- lostmsu 6y agoWhy aren't you doing A/B?
- fowl2 6y agoWhat would be the evaluation metric? Certainly measures like "engagement" could give exactly the opposite signals - hide everything behind more clicks and you'll get a lot more clicks!
- verdverm 6y agoMy clicks will be going away Google did us a favor and made an awesome Golang client library specific to GitHub https://github.com/google/go-github https://github.com/google/go-github
- onion2k 6y agoShould Github ever decided to do a/b testing I hope it's done either per repo or per organisation rather than per user. The last thing I want is members of my team having different views of our work.
- ljm 6y agoI had access to the design by flipping a switch under the 'feature preview' section of my profile menu. Had a little notification blob prompting me to see what was in there.
- dilap 6y agoIn what ways do you consider the new design to be better?
- threeseed 6y agoIf only there was a "Feature preview" option where you could ask users and the community what they think about design changes before they go live. Oh wait you have that. You just rolled it out for a couple of weeks basically to see if there were any showstopper bugs before you went live. I don't expect companies to take on my feedback. I do expect them not to treat it like it's a joke.
- verdverm 6y agoTo follow on, many of us felt this was rushed through and that our feedback was not heard. You can sense the frustration in the parent to this comment. You destroyed much of the trust I had. Will you roll this back and reconsider after talking more of your user base?
- wadkar 6y agoAgreed, I gave feedback but no use. I am not wasting my time when they’re not going to even bother listening to my feedback. I am out of the previews, not doing your QA for free.
- tester756 6y agoI think new UI is eyes exhausting at nights... I changed 2 things and that's the result: https://i.imgur.com/RU0rsAO.png https://i.imgur.com/RU0rsAO.png Disable: `border-top: 0 !important;` from .border-top-0 Set this class to this value: .color-blue-3 { color: rgba(3,47,98,.5) }
- Firehawke 6y agoI have a light sensitivity condition; large patches of white really hurt to look at for any real amount of time. Please consider implementing an optional dark variant in the vein of https://github.com/StylishThemes/GitHub-Dark https://github.com/StylishThemes/GitHub-Dark as an option.
- natfriedman 6y agoIt's coming.
- delfinom 6y agoWould have been nice that it was deployed as the same time as a new layout that's completely harsh on the eyes.
- ryanjodonnell 6y agoCant wait!
- Fire-Dragon-DoL 6y agoAmazing! Been waiting for it for a long time. I spend a lot of time on github!
- deleted 6y ago[deleted]
- Siira 6y agoA Solarized-light style one (similar to HN's background) would also be nice. Text becomes blurred for me in dark mode, and the white backgrounds are too bright.
- anticensor 6y agoMultiple dark themes, if possible: Solarized Grey dark *Pitch dark (also swap the roles of blue and yellow, except for the yellow light seen in the CI)
- balladeer 6y agoCan I ask why did you people bring those design changes - this one and the last instalment as well? Was there some real need, some market research behind it, or just an itch to do something? To be honest both these iterations feel like trying to fix something that's not even broken.
- verdverm 6y agoWhat about the contrast reduction issues that this design change incurs. Did you think about those of us who have poorer vision? What are you going to do to make GitHub more readable for those with disabilities again?
- bau5 6y ago> We are pro information density at GitHub. We are against locking children up in cages at GitHub.
- mkj 6y agoThe density has increased with things that aren't useful. You're browsing the file listing page (<> Code tab) but it now has a bunch of extraneous stuff on the right hand side (Did you know that this repository has 0.5% Perl code??). Also the most prominent bit is the bold #105 in the commit message - who cares about the handcrafted comment, the important thing is the Github specific pull request number.
- tarboreus 6y agoAgreed about the right column. Distracting and leaves much less room for what matters, typically a README.
- peternicky 6y agoAbsolutely spot on.
- verdverm 6y agoStarted a thread on twitter to see if we can get more questions answered or an answer to when we might https://twitter.com/verdverm/status/1275627757993484290 https://twitter.com/verdverm/status/1275627757993484290 https://news.ycombinator.com/item?id=23623601 https://news.ycombinator.com/item?id=23623601
- meristem 6y agoVery curious here: Can you tell us what the user interviews indicated, what were the personas and problem to solve, and successes/challenges usability tests uncovered?
- purrplexed 6y agoThanks for taking this into consideration. You can move stuff around for years and it wouldn't bother me. Lowering that bit of information though is a big pain.
- tarboreus 6y agoReally hate the second column on the right, which for a long README or documentation does nothing but make it so that there's less room for the text. I frequently use GitHub to store and read notes or to create larger docs, this essentially kills my desire to do any of that and makes me want to move what I have. The information in that column is also extremely low value.
- hackerman123469 6y agoNot only that but it also feels like everything is floating left. (Which it is but when there's nothing on the right scrolling down it looks out of place.)
- jmcvetta 6y agoAgreed - the right column is a waste of screen space and makes the reading experience generally unpleasant.
- deleted 6y ago[deleted]
- zoomablemind 6y agoAlso there's font-size party happening on the home's right sidebar. 16px, 14px, 12px in a rapid succession. Meanwhile, on Pull Requests' right side bar everything is rendered in 12px size. Just to be clear, 12px is equivalent of 9pt. That's fairly small on screen. For comparison the README body text is rendered in 16px, which is equivalent of 12pt. By the way, HN body text is 13.33px, about 10pt.
- deleted 6y ago[deleted]
- niutech 6y agoThere are bugs in IE 11 (which has 5.88% usage on desktop according to NetMarketshare and is still supported by MS) - dropdown buttons and other interactions do not work due to JS errors: SCRIPT1053: Const must be initialized SCRIPT1014: Invalid character SCRIPT1010: Expected identifier SCRIPT1003: Expected ':' Please fix them.
- vimslayer 6y agoHow much of those IE users are also users of GitHub? Shipping more modern EcmaScript versions than what's supported by IE has lots of advantages for users whose browsers can support it, so I'd hate it if the IE support came with the expense of everyone else's experience. There are ways to serve different JS bundles for different browsers, of course, but that comes with a maintenance cost for them. Weird though that some buttons wouldn't work at all, because at least most of the basic functionality seems to work fine with JS disabled even. Maybe they should just disable JavaScript altogether for IE and it'd work better. That should be easy to implement too.
- twistslider 6y agoGitHub dropped support for IE in July 2018: https://twitter.com/michlbrmly/status/981855020948877312 https://twitter.com/michlbrmly/status/981855020948877312
- ljm 6y agoWow, already fixed! That's fantastic :)
- verdverm 6y agoNothing is fixed
- cootsnuck 6y agoI just want to echo what others are saying about the sidebar on the right. It feels like it's taking up way too much real estate without offering much value. The most important information feels constricted to me. I'm sure as I get use to the new design I'll be able to navigate without much issue, but still figured it's good to share with ya. Thanks for gathering feedback!
- verdverm 6y agoSeems like it might be continued ignoring of our feedback. Nat drive-by commented on a non critical comment. Did not address our main concerns. Did not say anything like "let us take all this in and come back with something articulate" either... Definitely feel like Nat and GitHub are actively ignoring is at this point
- biblioman 6y agoI'd urge you to keep accessibility in mind. I have a bit of an issue with processing visual information, and the fact that the files don't have any borders on them now makes it really difficult for me to process which file has which status. Having toggleable borders (horizontally and vertically) would be a huge improvement in terms of accessibility. It'd also be nice if you could have the bar at the side up top, or shrink it a lot. It takes up a quarter of the screen space plus padding and margin. For reading README.md files and Awesome Lists, it's extremely intrusive. Alternatively, you could have the README.md below the longer element of the new "sidebar" and the file list, so that it can take up the whole width of the screen. I hope you read this!
- danudey 6y agoFWIW, on a 1440p monitor, there's a huge amount of wasted/empty space, which means that the things that the space is used for should be pretty critical or it seems like a colossal waste overall. Here's my input. Maybe it's useful? I don't know. https://imgur.com/a/S9YRBq0 https://imgur.com/a/S9YRBq0
- justinclift 6y agoFor the "Why don't these line up?" pieces, it looks like the new layout was designed for window width of about 1350 pixels. When the browser window is that wide (for FF anyway), the whole layout seems to line up well. When the layout is wider than that (eg full window width), there is unbalanced white space all around.
- nyanpasu64 6y agoThe old layout wasted more space on the sides. But I agree the new layout's top bar is misaligned.
- FrozenVoid 6y ago> pro information density I have to use CSS to remove empty gaps on both sides.
- Mindwipe 6y ago> Also – I don't think there is a principle of lowering information density at work here. If there isn't you've done a tremendously bad execution job and no testing.
- esimov 6y agoBring back the old Github! The new look is a mess.
- gillyb 6y agoWow, I think you didn't get enough credit here for replying to this thread! Kudos to you! I personally like some aspects of it and dislike some other, but nothing major in my opinion. What I can say is that only recently I started using the 'Projects' feature and it's really awesome! Amazing work, and assuming you're the real 'natfriedman' it's amazing you answered!! :)
- flowerlad 6y agoChange is bad unless it is great. Don't make changes just because your designers need something to do. When you make design changes your customers must immediately love it, if not it is a bad change. When it comes to design, there is no such thing as a "good change", there are only bad changes (the default) and great changes.
- jb3689 6y agoI agree with this. Taking on a "UI overhaul" of something folks don't see as a problem is just inviting them to try other tools. A lot of devs love using Github already - why up-end them?
- imdsm 6y agoLittle late to the party here but I am a heavy user of GitHub both personally and at work, and these recent changes have made it much less enjoyable, usable, and efficient. I feel as though they were driven by some need to refresh the look of GitHub, but not by the need of the users. And this I think is the biggest mistake here. If you have roughly 40,000,000 active monthly users — how many of those do these design changes serve? And how do they serve them? That's what I'd be asking now if I was on your team.