"GitHub" Is Starting to Feel Like Legacy Software - The Future Is Now
www.mistys-internet.website
I’ve used a lot of tools over the years, which means I’ve seen a lot of tools hit a plateau. That’s not always a problem; sometimes …

Not my blog, but the author’s experience reminded me of my own frustrations with Microsoft GitHub.

  • Eager Eagle@lemmy.worldEnglish
    563·
    3 months ago

    There are quite a few things I don’t like about GitHub, but calling it legacy makes no sense.

      • tyler@programming.dev
        91·
        3 months ago

        both of those aren’t websites. I use fork though and had no clue you could do that. I’ve needed that like 10 times in the last week alone haha

      • fmstrat@lemmy.nowsci.comEnglish
        5·
        3 months ago

        I am about to make you very happy.

        alias gl='git log --graph --abbrev-commit --no-decorate --date=format:'\''%Y-%m-%d %H:%M:%S'\'' --format=format:'\''%C(8)%>|(16)%h  %C(7)%ad  %C(8)%<(16,trunc)%an  %C(auto)%d %>|(1)%s'\'' --all'
        • spartanatreyu@programming.dev
          2·
          3 months ago

          I use git log --graph --all --remotes --oneline whenever I need to shell into another computer, but it’s still too barebones for regular use.

      • Kissaki@programming.devEnglish
        51·
        3 months ago

        I was thinking “oh, network view, this is gonna be a good example”, but that comparison isn’t.

        What specifically do you think is legacy in that comparison? The coloring? The horizontal layout? The whitespace?

        The network view lays out forks and their branches, not only [local]/[local+1-remote] branches.

        I don’t know what IDE that miro screenshot is from. But I see it as wasteful and confusing. The author initials are useless and wasteful, picking away focus. The branch labels are far off from the branch heads. The coloring seems confusing.

        bg looks like the same

        • spartanatreyu@programming.dev
          2·
          3 months ago

          What specifically do you think is legacy in that comparison? The coloring? The horizontal layout? The whitespace?

          Note: I’ve changed the first link from https://github.com/cxli233/FriendsDontLetFriends/network to https://github.com/zed-industries/zed/network. Still the same view, but just a different repo to highlight the problems

          1. It’s in a small non-responsive box
          2. Ridiculous spacing
          • If you want to see the commit messages, you either need to hover over a dot which increases visual scanning durations or you need to go to the commits view which only shows the commits on a single branch
          1. It doesn’t show commit messages
          2. It’s scrolling horizontally
          3. Branches cannot be collapsed
          4. Branches cannot be hidden/ignored
          5. No way to search for commits
          6. No way to select multiple commits
          • Which also means no way to diff any specific commits together
          • And there’s also no way to perform an action over a range of commits
          • And there’s also no way to start a merge/merge-request/pull-request/etc… between two commits
          1. No way to sort by date/topologically
          2. Keyboard controls only moves view instead of selecting commits

          I’ll stop here at 10 reasons (or more if you count the dot points), otherwise I’ll be here all day.

          The network view lays out forks and their branches, not only [local]/[local+1-remote] branches.

          Yes, but the others can do that while still being usable.

          I don’t know what IDE that miro screenshot is from. […]

          It’s gitkraken

          […] But I see it as wasteful and confusing. The author initials are useless and wasteful, picking away focus. The branch labels are far off from the branch heads. […]

          The picture doesn’t do it justice, it’s not a picture, it’s an interactive view.

          You can resize things, show/hide columns, filter values in columns to only show commits with certain info (e.g. Ignore all dependabot commits), etc… Here’s an example video.

          […]The coloring seems confusing.

          You can customise all that if you want.

      • JackbyDev@programming.devEnglish
        3·
        3 months ago

        Do either of those tools show logs across forks though? The first link is a totally different purpose than the second two.

        • spartanatreyu@programming.dev
          1·
          3 months ago

          The first link is a totally different purpose than the second two.

          The first link is going to there because that’s the only graph view that github has.