jj (Jujutsu)

“whose workspaces track what state they were snapshotted at, thus never losing what the true diff of a workspace should be”

“I'm having a much better time with jj and a workspace per subagent than I was with git and worktrees.”

“tools like jj remove the need in Git GUI because mental model and UX gets streamlined”

“when I use filesystem paths as remotes they need to be colocated or else it doesn't work, which is a little annoying”

“the goobers finally buckle down and read the manual for a tool that coincidentally does stuff a little different from git”

“those same people that struggled for years with git are able to pick up jj and be very productive with no issue whatsoever, in a matter of days”

“brings nothing new to the table while desperately trying to replace a well-established industry standard”

“doesn't really differentiate itself enough for people who've been using git for a long time”

“There is no jj command that destroys information another jj command can't bring back.”

“I think the project would find many more fans if it didn't make such a big deal about being kinda like git.”

“jj has far fewer warts than git. You don’t have to learn every jj idiom, you just have to find a workflow you like”

“once you start doing the really fancy stuff, one of the two will get you a lot fewer messy explosions”

“in jj, they don't disappear - they remain very visible, and the log UI shows them in a way that makes it clear where they come from”

“This is such a killer feature to me. I'm not scared to start potentially gnarly rebases anymore because I can painlessly undo.”

“With branches, jj is to git what git was to SVN. It's an order of magnitude less friction to do branching in jj than git.”

“I found that jj is just so much nicer to use, for me, that I haven't used git itself in years at this point.”

“as far as I can tell you still need to run Cargo which I don't want to do because I don't care about Rust”

“Anonymous branches are amazing for when you are trying out a bunch of different approaches to a problem.”

“it's frustrating that lfs is taking so long. But there seems to be some momentum recently”

“It's like git with a lot of accidental complexity (staging area, stashes, commit ID instability) removed.”

“There is nothing in jj, pijul, or Bram Cohen's thing that is anywhere near as dramatic a quality of life improvement”

“it hasn't felt sufficiently better than git to justify bothering re-learning this stuff”

“jj is better for some workflows, which, if you're a git expert as you claim, you conciously or subconciously avoid as 'too much work' or 'too brittle'.”

“These obscure nonsense commands only makes sense when you are accustomed to them.”

“I'm having trouble understanding the value of this and most other supposed advantages of jj I'm seeing.”

“rebases don't lose branches and jj absorb trivially squashes changes to the correct head”

“the workflows are intuitive and you never find yourself reaching for help to get something done”

“The mental model is so much cleaner than git, undo actually works the way you'd expect it to”

“jj has almost 30,000 stars on github. You might not be looking for a different git ux, but plenty of people are!”

“trivially working on 3 PRs in a single checkout and pushing focused changes to each one independently”

“seems a lot easier to learn, but really don't have the interest to re-learn a bunch of ever-changing idioms”

“I won't install Rust just to test your software. Make a debian package like everyone else.”

“The only time I had any friction was on a team where stale code-gen output was checked into the repo”

“I'd argue that this is one of the killer features of `jj`, since by comparison `git rebase` treats everything the same”

“It's very intuitive in my experience, something I can't say is true for managing git commits”

“Just being able to squash changes to earlier commits without having to fiddle with fixups and interactive rebases is worth it for me.”

“I also like `jj commit [paths]` to commit just a subset of files when I don't need hunk based splitting.”

“jj shows you can do that also without blocking on merges but with first level conflicts that need to be resolved”

“I'm advocating for JJ to build a proper daemon that runs "checks" per change in the background.”

“because children are also rebased, you can see immediately how much work, if any, you have to do”