If Jujutsu ever picks up steam and becomes a replacement of Git, I wish the Github version for it will be called Kaisen.
or somebody write a backend and name it Kaisen
Jujutsu (jj), a Git compatible VCS
111–117 of 117 posts
Re: Jujutsu (jj), a Git compatible VCS
#112The extents people will go to, to avoid having to spend a morning learning git
why bother learning to bike when you can walk? why bother learning to drive when you can bike? How's COBOL and Fortran doing these days?
Re: Jujutsu (jj), a Git compatible VCS
#113I'm still unsure of why I'd want to move to jj from git. My ideal git workflow is pretty simple: 1. `git switch -C new-branch` 2. Make changes, time passes 3. `git add .` 4. `git commit -m "Description of changes made"` 5. `git fetch && git rebase origin/main` 6. `git push` 7. Make pr to main If main is out of date I rebase again to update. This to me feels pretty light weight and is not a hinderence in any way on my…
Funny thing, I'm becoming an evangelist of Jujutsu but somehow I found myself stuck for 30 minutes with Jujutsu not being able to push a desired branch/commit, and Jujutsu had made my local git copy in detached HEAD. In the end I created a few useless branches through jj, and was still not able to articulate or understand through the docs how to sort my situation and tell jj that I want to move my latest work on main, nor to find a way to rebase/merge my accidentally created bookmarks/branches on top of main. Then ended up switching back to git, redo all the coding again and push.
Having to understand either jj or git models through tons of tutorials and videos, while I just want a way to dialog easily with my changes in my own vocabulary and my own mental model, make me believe I'm a lost cause or I need my own VCS
Anyway Jujutsu stil feels great, I just hope now to not need to suffer like I did with git.
Re: Jujutsu (jj), a Git compatible VCS
#114Earlier quoted context omitted.
> why would the contributors to jj not just try to make git better by addressing these weaknesses? Because jj isn't being built to improve git, but to allow using git at Google to work on Piper-backed code instead of hg/fig, and adding support for the abstractions that are needed to support git and piper was probably seen as free complexity on git's side.
This is slightly incorrect. I started it because I believed in the idea of modeling the working copy as a commit, but it's true that I made the storage pluggable from the beginning because I wanted to be able to convince my team at Google that we should use it internally too.
I thought it was simply a response to git5/git-multi getting deprecated once fig became popular.
I'm a bit surprised then, that's one of the things that has kept me from trying it as it feels weird to not have that much control over what gets into the commit. Using magit doesn't help as it's just way too good once you get used to it.
Re: Jujutsu (jj), a Git compatible VCS
#115Earlier quoted context omitted.
Because every person in here who’s actually used jj is telling you straight up that it’s less complicated. Using jj is less complicated in—as far as I can tell with six months of conversion—actually 100% of the time. I spent one day adapting and maybe two week of having to look something up every other day. And now all of git’s infamous pain points are gone. There is no index. There is no stash. Rebase conflicts are…
Okay, happy it works for you. Still don't see a point.
The point for me is to build better and remove the need to know so much about vcs. Git is powerful but requires too much knowledge about git itself to get things done or to tackle possible conflicts in collaboration. Jujutsu tried to remove some of the concepts or make a better ui, to remove some complications. It's like providing an abstraction like python instead of C. Yet it's not perfect.
I also struggle to transition to jujutsu yet I admit some benefits. But honestly both are yet too complicated and error prone for something as basic as communicate changes and align versions with each other. I'm happy to see initiatives such as jj but it's still an alpha.
Re: Jujutsu (jj), a Git compatible VCS
#116Earlier quoted context omitted.
The upside with jujutsu though is that it's completely compatible with Git and you can work on the same repository with Jujutsu while your coworkers use Git. This allows the people who want the 15% gain to have it, while not forcing anyone to do a costly migration.
I know people who really hate git because the UI is so awful, and it’s (theoretically) way more than a 15% gain for them. They’ll get to stop rubbing broken glass against their legs every day.
Git feels like solving puzzles everytime there are branches or collaboration made on a repo.
So every day. Most productive days are when I dont need to use git.
JJ is a workaround for git pains but the UX is not mature enough for replacing git yet.
Having distinct local working copies of same repo per git branch still works great, not stash needed, no conflicts or pain with local wip and drafts changes overwritten by pull. No blocker for switching branches. No reset hard/soft whatever. And makes files comparisons easier and makes my git workflows easier.
I still feel vcs could be simpler and solved problem if more engineers care about the topic of vcs and generally speaking about the ux of their main tools instead of creating new TUI and plugins to workaround broken ones.
Re: Jujutsu (jj), a Git compatible VCS
#117I've so far failed to see why jj needs to reimplement git to add some UI pleasantness.
To me, the real value I saw when playing with jj was the drag-and-drop change history manipulation in the `gg` GUI app -- and as far as I can tell, that could just as well live directly on top of git.