I used CVS and ClearCase before moving into Git, and it took me some time to adjust to the fact that the cost of branching in Git is much much less than ClearCase. And getting into the “distributed” mindset didn’t happen overnight.

  • madcaesar@lemmy.world
    911·
    6 months ago

    Wft isn’t there just a nice clean git UI that tells you in human terms what you are doing.

    Command line interfaces suck ass.

    • smegEnglish
      51·
      6 months ago

      I think the lack of UI is the main reason for all the jokes about git being horrible to learn. Fork is a pretty good client, and there are also some pretty good VSCode plugins to show you how all the commits and branches fit together.

        • FizzyOrange@programming.dev
          3·
          6 months ago

          Tbf I’ve been using Git for at least 10 years and I only just discovered this. I think nobody talks about it because it doesn’t show history which is 90% of the reason to use a Git GUI.

          • lysdexic@programming.devEnglish
            1·
            6 months ago

            I think nobody talks about it because it doesn’t show history

            What do you mean it doesn’t show history? It’s perhaps the only thing it handles better than most third-party git GUIs.

        • smegEnglish
          11·
          6 months ago

          git: 'gui' is not a git command. See 'git --help'.

          If you’re going to try to smack talk like Linus Torvalds then maybe check your facts first

      • FizzyOrange@programming.dev
        1·
        6 months ago

        I’ve tried them all. Didn’t get on with Sublime Merge.

        My recommendations:

        • GitX (sadly Mac only, and a confusing array of forks).
        • Git Extensions (which I avoided for ages because the terrible name makes it sound like it’s just explorer shell extensions but it’s actually a full GUI).
        • Git Graph VSCode extension

        Most of the others are kind of crap IMO.