Live data from Hacker News

Switch to Jujutsu Already: A Tutorial

stavros.io

131–140 of 164 posts

Re: Switch to Jujutsu Already: A Tutorial

#131
> since its commands were an inscrutable jumble of ill-fitting incantations, and it has remained this way until today

What command is he talking about? When you get that git is a graph manager, it gets really easy to manage, very quickly..

Re: Switch to Jujutsu Already: A Tutorial

#132

> since its commands were an inscrutable jumble of ill-fitting incantations, and it has remained this way until today What command is he talking about? When you get that git is a graph manager, it gets really easy to manage, very quickly..

I thought so as well. A long time got seemed quite mysterious, but after I understood what git actually was, it became very coherent and the naming became intuitive.

Also, while I think the UI of git can be improved, it is not more complex than it needs to be.

Re: Switch to Jujutsu Already: A Tutorial

#133
post #51

Earlier quoted context omitted.

git is both a (bad) UI and a protocol. Jujutsu is a UI on top of git (the protocol). There's nothing wrong with taking the time to learn how to use a bad UI, especially if there's no other option. But don't mistake your personal mastery of git for evidence that it's better than jj. In all likelihood, the git proposal you allude to would not extend further than adding a bit of persistent metadata that follows commits…

Small point of order, jj is a VCS with a pluggable backend, one of which is git. That’s a bit different than a UI on top of the git protocol.

Isn't git the only supported backend?

I always introduce jj as a better git ui.

Re: Switch to Jujutsu Already: A Tutorial

#134

Earlier quoted context omitted.

Of course! Likewise, you can do in C++ everything you can do in Rust. And yet Rust is there and fast growing in popularity. As it turns out, how to do things, and at the cost of what externalities, matters no less than what you can do.

I don't like C++ either, but yes that is also my opinion about Rust. I do already annotate ownership semantics in C, so I don't know why I need a compiler that is opinionated and tells me how I should structure my code. I think Rust would invoke much less resistance, if it weren't so opinionated. As for jj, JJ and Git are much more close than C and Rust. JJ tends to have slightly less commands, but only because what…

> The impression I get from these posts, is that it would have been doable with similar effort in Git, but they just never bothered.

I don't think it would have been doable. I hear this question/comment sometimes. I sent https://github.com/jj-vcs/jj/pull/7729 to have a place to point people to.

Re: Switch to Jujutsu Already: A Tutorial

#135

I have primarily used git in the terminal for more than a decade. I also used magit when I was primarily working in emacs (magit's great!). I now primarily use lazygit. While I'm not a fan of the whole UI, this is the only git tool that makes me go super fast while creating a near-perfect commit history. I tried using jj but immediately stopped after installation as it required a learning curve that I wasn't ready to…

If you use Emacs, there's a mode similar to magit that's under active development: https://github.com/bolivier/jj-mode.el

Re: Switch to Jujutsu Already: A Tutorial

#136
Every time I read about someone's woes with git I have no idea how people run into certain scenarios or what people are even talking about, it reads like "if you've ever tried to unfrobnicate all non-downstream flanges without rebasing your head ref onto the flange upstream of your commit, you'll know this is really hard to do in git", I just think great I have never tried to do that in 20 years of git usage and have no idea what I'd want to, I'm just going to keep using the same ~5 commands and avoiding complexity which has served me well and allowed to avoid any crazy vcs issues that seem to plague other developers

Re: Switch to Jujutsu Already: A Tutorial

#137

Earlier quoted context omitted.

Small point of order, jj is a VCS with a pluggable backend, one of which is git. That’s a bit different than a UI on top of the git protocol.

Isn't git the only supported backend? I always introduce jj as a better git ui.

They support Gerrit, Google's internal VCS.

Re: Switch to Jujutsu Already: A Tutorial

#139

Earlier quoted context omitted.

Small point of order, jj is a VCS with a pluggable backend, one of which is git. That’s a bit different than a UI on top of the git protocol.

Isn't git the only supported backend? I always introduce jj as a better git ui.

It's the only open source backend right now. Google's backend for their VCS infrastructure is still private.

Re: Switch to Jujutsu Already: A Tutorial

#140

Every time I read about someone's woes with git I have no idea how people run into certain scenarios or what people are even talking about, it reads like "if you've ever tried to unfrobnicate all non-downstream flanges without rebasing your head ref onto the flange upstream of your commit, you'll know this is really hard to do in git", I just think great I have never tried to do that in 20 years of git usage and have…

That's how I started, but there's big advantages to workflows that are easy to mess up using got, but more natural with jj.
Post reply on HN