this post was submitted on 29 Sep 2025
103 points (84.6% liked)

Programmer Humor

26640 readers
1930 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 

you are viewing a single comment's thread
view the rest of the comments
[โ€“] dfyx@lemmy.helios42.de 7 points 1 day ago* (last edited 1 day ago) (1 children)

If I remember correctly, they used to be ~~in a tab in the top navigation, together with "Code", "Issues", "Pull requests", etc.~~ which was a lot easier to find for people who are not familiar with GitHub's UI. Edit: it was a separate bar right above the file list, together with the number of commits and branches: https://web.archive.org/web/20180610234228/https://github.com/rails/rails

Same problem with forks / network. In earlier revisions of GitHub's UI, they were relatively easy to find. Now you have to know that you can click the "59.7k forks" sidebar text which is in no way styled like a link or button. You can just infer it from the fact that there are also "Readme" and "View license" in the same list.

[โ€“] dfyx@lemmy.helios42.de 9 points 1 day ago

Looking back, I find every single aspect of the 2018 design more accessible than the current one. Releases are above the fold, the list of forks is reachable by clicking the number next to the fork button, the explore link is right there in the top navigation. Sure, having three levels of horizontal navigation doesn't look very clean but there must be a better solution than hiding everything in hamburger menus and sidebars where you can only find them if you already know they exist.