Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Jujutsu: A Git-compatible DVCS that is both simple and powerful

github.com

Post reply on HN
Print view View original

21–30 of 269 posts

Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful

#21

Post by hosh »

dagurp wrote: post #11
zelphirkalt wrote: post #5

I would say "What a weird name for a VCS. Whether that will work ...", but then I have to remind myself of the dictionary meaning of "git". So who knows. Maybe we will be adopting all kinds of martial arts terminology. For example: "I use Karate to manage my code. I divide everything using chops. When a kata is done, ..."

It's a horrible name to pronounce for many non-English speakers.

Ironic because it’s a Japanese name, not English.

According to the readme, “jj” was chosen because it was easy to type, and a name was found to fit that.

Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful

#22

Post by ocharles »

Nice to see this posted here. I switched over to it about 2-3 weeks ago, and I haven't looked back. It took a lot of mental rewiring, but I really enjoy the workflow `jj` provides. There's no longer a time to think about what's being committed, because all file changes automatically amend the working copy commit. Of course, sometimes you don't want this, so you have things like the ability to split a commit into two, moving commits, etc. But having _everything_ operate on commits is really nice! Other niceities that I like:

- `jj log` is awesome for getting an overview of all your branches. If, like me, you have a lot of work in progress at once, this provides a great map

- Conflict resolution is really cool, as you can partially resolve conflicts, and then switch branches. Conflicts are also tracked specially, but I haven't done too much with this yet.

- The abbreviated changeset ids are really handy. I often will just `jj log` (or in my case just `jj` as that's the default), notice a changeset I want to rebase, then run `jj rebase -s qr -d master`. `qr` here is an abbreviated changeset id for a branch/commit, and usually much quicker than typing the branch name out! This will probably change when clap gets updated to support dynamic tab-completion though.

Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful

#24

Post by TylerE »

ocharles wrote: post #22

Nice to see this posted here. I switched over to it about 2-3 weeks ago, and I haven't looked back. It took a lot of mental rewiring, but I really enjoy the workflow `jj` provides. There's no longer a time to think about what's being committed, because all file changes automatically amend the working copy commit. Of course, sometimes you don't want this, so you have things like the ability to split a commit into two,…

What happens if you accidentally save a file with some sort of secret that gets sucked in?

Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful

#25

Post by brmgb »

robertlagrant wrote: post #14
gautamcgoel wrote: post #12

I am certainly no expert in version control systems, but I've gotta say that it's really wonderful to see a project that builds on the algorithmic and cultural successes of Git but with a simplified and modernized approach. The reason that Git took over the open-source world is two-fold: first, it was adopted by Linux, which ended up being the most influential OSS project of all time. Second, the Git model, which is…

> which is distributed and egalitarian at its core, is a better model for a fast-paced, globally distributed community of developers than previous monorepo systems like Mercurial I'm a bit confused by this. I don't think that's what monorepo means, is it? Monorepo is what you choose to put in a repo? And I thought Mercurial was extremely similar to Git as it's also a DVCS?

It is. The OP is wrong, probably because he has never used Mercurial, which wouldn’t be that surprising given it doesn’t have a lot of users outside of the few remaining companies still using it.

Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful

#28

Post by awestroke »

"working copy is automatically committed" seems like a good idea at first glance, but there are many situations where this is not a good idea:

- when new artefact files are added and you have not yet added them to .gitignore, they'll be automatically committed

- when you have added ignored files in one branch and switch to another branch, the files will still be in your working copy but not listed in your .gitignore file, and would then be automatically committed

- staging only some files and comitting is much easier than splitting a commit after the fact

Re: Jujutsu: A Git-compatible DVCS that is both simple and powerful

#30

Post by jimsimmons »

This project is a great example of subliminal marketing.

It is less apparent now but still, the repeated flex of “Google”, 20% project etc when no typical reader would assume them is classic corporate charlatanry.

Shame because I like the project otherwise

Post reply on HN