<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>natfriedman</author><text>Thanks for the feedback about the latest commit status. This is something we should definitely fix.&lt;p&gt;Also – I don&amp;#x27;t think there is a principle of lowering information density at work here. I think it&amp;#x27;s just a design that we will keep iterating. We are pro information density at GitHub.</text><parent_chain><item><author>ljm</author><text>I 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&amp;#x27;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.&lt;p&gt;When I&amp;#x27;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&amp;#x2F;status checks now. Those things should be first class citizens, that&amp;#x27;s why we put status badges all at the top of our readmes to make that info more visible with what we have.&lt;p&gt;It follows the trend of designing with lower information density. This trend IMO is not appropriate for developer tools.</text></item></parent_chain></comment><story><title>Ask HN: Thoughts on new GitHub layout?</title><text>I think it feels like Jira and I&amp;#x27;m really sad. Seems more like a MS move than a GH move...&lt;p&gt;Migrating to gitlab...</text></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>fxtentacle</author><text>I find it much more difficult now to line up filename and last modified time in the file browser.&lt;p&gt;And I agree on the low density. Plus it now looks like a children&amp;#x27;s toy, not like a work tool. A while ago, there was an article on HN about kawaii cuteness culture sneaking into everything. It appears that has happened here.</text><parent_chain><item><author>ljm</author><text>I 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&amp;#x27;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.&lt;p&gt;When I&amp;#x27;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&amp;#x2F;status checks now. Those things should be first class citizens, that&amp;#x27;s why we put status badges all at the top of our readmes to make that info more visible with what we have.&lt;p&gt;It follows the trend of designing with lower information density. This trend IMO is not appropriate for developer tools.</text></item></parent_chain></comment><story><title>Ask HN: Thoughts on new GitHub layout?</title><text>I think it feels like Jira and I&amp;#x27;m really sad. Seems more like a MS move than a GH move...&lt;p&gt;Migrating to gitlab...</text></story>