22
Introduction - Steve's Tutorial on jujutsu, an alternative front-end to git
(steveklabnik.github.io)
this post was submitted on 14 Jul 2025
22 points (89.3% liked)
Programming
21556 readers
200 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would be curious to know in which specific cases people which have experience with using both think plain git is still better.
In my experience, when using jujutsu it can be necessary to use git commands to access repos via ssh, vpn and such. Also, jujutsu ignores git submodules, so one has to do submodule operations with git (but I think that culturally, using submodules most often is not such a good idea).
I don't have experience with Jujutsu, but I always have the same problem with these alternative frontends, which is that I'd still want to be proficient with the original. If you need to look up how to fix something or you want to help others in your team or you want to script something, then the language to speak is simply the Git CLI.
And I don't feel like I even use the Git CLI enough where a different tool could be so much better that it's worth learning both.
Obviously, your priorities may differ, but yeah, that's just always the reason for me why I prefer the Git CLI, even if it were objectively more difficult to use.