210
Let's Make Sure Github Doesn't Become the only Option - Edward Loveall (blog.edwardloveall.com)
submitted 11 months ago by to c/programming@programming.dev
38 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 11 months ago (2 children)

Jujutsu is another git alternative I keep seeing around and came to mind reading this:

https://steveklabnik.github.io/jujutsu-tutorial/introduction/what-is-jj-and-why-should-i-care.html

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 25 points 11 months ago (3 children)

    Why? This is isn't about git. It's about github. Two completely different tools.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 6 points 11 months 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 11 months ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 10 points 11 months ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 11 months ago

    I gave a try to jj. It's fine for personal projects or small team and make the workflow a bit easier. No more "git add; git commit; git push" each time you do a modification. You just "jj git push" and everything will be automatically pushed.

    However, the biggest criticism I have is that he doesn't encourage to push every time. It really encourages you to keep your modif locally and push only to create a PR, and that's not a good approach.

    Even if you code is WIP, even if everything crash, you really should push your code to backup it. Who cares ? As long as it is not on master branch, it's your own mess.

  • permalink
  • fedilink
  • source
  • parent