• limer@lemmy.ml
      52·
      12 days ago

      I think it’s valid unless one thinks git should be the only standard. Looking at other tool chains opens options

      • Ephera@lemmy.mlEnglish
        4·
        12 days ago

        Jujutsu is a Git frontend, from what I understand, much like there’s tons of Git GUIs. So, you interact with it in a different way, but you still push to a Git repository and others can interact with your code by using Git.

        I guess, it somewhat lessens the grip of Git, because they can hook different backend services (e.g. Subversion, Mercurial, Fossil) into this frontend, and from what I understand, they plan to develop an own backend eventually. But yeah, for now, the communication standard is still Git.

        • Anti-Antidote@lemmy.zip
          3·
          12 days ago

          It’s not a Git frontend per se, it just uses Git as a storage layer (Google’s internal backend doesn’t use Git and behaves more like a commit cloud)

    • IanTwenty@lemmy.world
      3·
      12 days ago

      I know. The author suggests:

      Experiment with new-to-you version control systems like Fossil, Mercurial, and Pijul.

      The author is:

      learning about different version control systems. For example, the differences between Fossil and git revealed a lot of my biases towards git simply because it’s familiar (and Fossil seems really cool). Reading about the theory behind Pijul absolutely bends my brain into knots. I keep trying anyway because conflicts in git are frustrating and I’d like a better solution.

      The author says:

      It would be nice to move beyond git one day and have a better experience for managing complex codebases, and not on GitHub’s timeline.