Jujutsu at Google [video] • Hacker News Board

Re: Jujutsu at Google [video]

#51

Post by gpm » Thu, Oct 30, 2025, 9:23 PM UTC

shmichael wrote: post #45

I'm trying to understand, would jj's first class conflicts solve the issue of having "stacks" of PRs that can easily be updated at any point in the stack? This is one of the features most absent from git, but prevalent in Google's tooling as well as Meta's. The only good known solution I know is graphite.dev

Not 100% sure I understand what you're saying, but I think the answer is "yes".

You can modify any* commit in `jj` regardless of whether it has commits on top of it at any time. Either by another commit into it, or by directly checking out the commit and editing the source tree. If this creates conflicts with commits on top of it `jj` just records those commits as having conflicts/adds conflict markers without interrupting the workflow.

* Commits pushed to remotes are marked immutable so you have to pass an extra flag to say ignore that and modify them anyways. Which you generally wouldn't want to do.

Re: Jujutsu at Google [video]

#52

Post by qalmakka » Thu, Oct 30, 2025, 9:23 PM UTC

Ferret7446 wrote: post #13

kyrra wrote: post #8

Earlier quoted context omitted.

This talk is focused on JJ within Google. This is a Google-internal only GA. JJ is available externally just fine. Google is mainly a linux-dev shop, with all other platforms being second-class citizens.

Not that there are any other options. You're not gonna run datacenters on Mac boxes or Window s, nor would you want to pay a Unix vendor

> UNIX vendors

Well FreeBSD exists, just look at Netflix

Re: Jujutsu at Google [video]

#53

Post by gpm » Thu, Oct 30, 2025, 9:25 PM UTC

jeffbee wrote: post #48

stonogo wrote: post #33

Earlier quoted context omitted.

Because you work for Google, or because you don't want to wait for official git to be rewritten in Rust.

As I recall, git5 was such a piece of junk that they deleted it so nobody could use it any more. It had its fans but they were all deluded. It was a demonstrated fact that git5 users were less productive than normal g4 users.

What is/was "git5"? Git the vcs is only about to release version 3.0... Googling only reveals some gene that happens to be named that...

Re: Jujutsu at Google [video]

#54

Post by phainopepla2 » Thu, Oct 30, 2025, 9:33 PM UTC

BoorishBears wrote: post #30

Y_Y wrote: post #16

Earlier quoted context omitted.

Ugh, I'd prefer people keep passion for the bedroom and just convey information straightforwardly without trying to "sell" it to me. Adding a false excitement signal to the information is a hindrance to me as a viewer. If you want Tony Robbins then go and see him. If you want an overview of the new product architecture lets keep calm and get on with it.

The irony the deck presents 3 very different presenters to show that you don't need to be Tony Robbins to be passionate. If you can't be passionate, don't make it a presentation. Passionate doesn't need to mean over-the-top, but it means speaking on the topic effectively and in a way that reflects believing there's a reason for these people to sit there and listen to you. No one is forcing people to do presentations,…

> No one is forcing people to do presentations

To the contrary, pretty much every presentation I've ever given has been one that I would not have done if it were up to me

Re: Jujutsu at Google [video]

#55

Post by jeffbee » Thu, Oct 30, 2025, 9:33 PM UTC

gpm wrote: post #53

jeffbee wrote: post #48

Earlier quoted context omitted.

As I recall, git5 was such a piece of junk that they deleted it so nobody could use it any more. It had its fans but they were all deluded. It was a demonstrated fact that git5 users were less productive than normal g4 users.

What is/was "git5"? Git the vcs is only about to release version 3.0... Googling only reveals some gene that happens to be named that...

It was a way to pretend that you were using git when you were in fact using piper.

Re: Jujutsu at Google [video]

#56

Post by OkayPhysicist » Thu, Oct 30, 2025, 9:46 PM UTC

cosmosgenius wrote: post #41

dakiol wrote: post #18

I've worked in huge repos with hundreds of developers pushing code every day, dozens of MRs open per day, and all I always needed was a very limited set of what git is capable of (git commit, git co, git st, git merge/rebase, git log). To find bugs, I use "bisect but visually" (I usually use jetbrains IDEs, so I just go to the git history, and do binary search in the commits, displaying all the files that were affect…

one thing which causes problem with git for me is collaborative work without using "git server". This usually comes up at homelab situation with no access a "git server" or ssh server. One thing with jj is i can use existing sharing mechanism like dropbox, google drive or if nothing else just copying jj folder (granted all of those are bad idea w.r.t vcs but still).

My go-to solution for this problem is a git init --bare --shared=group repository in a shared mountable drive. Then you can declare that repo origin, and tada, git push/pull works.

Re: Jujutsu at Google [video]

#57

Post by [deleted] » Thu, Oct 30, 2025, 9:47 PM UTC

pinkmuffinere wrote: post #29

martinvonz wrote: post #10

Earlier quoted context omitted.

Thanks for the link. I went through it but I'm not sure what it's telling me to change. Can you elaborate? If it's "be more engaging", i think is unfortunately going to be hard to improve because this is just how i am.

I appreciate your frank oppenness to feedback! I'd like to give you some, but first I want to call out that (1) I'm certainly no expert and (2) you may have been voluntold to make a powerpoint on material that isn't well-fit for powerpoint. My feedback: - I think you could improve by being more excited / exciting (the Death By Powerpoint slide deck says "passionate"). Personally, I try to mitigate this problem by dri…

[deleted]

Re: Jujutsu at Google [video]

#58

Post by eddd-ddde » Thu, Oct 30, 2025, 9:47 PM UTC

shmichael wrote: post #45

I'm trying to understand, would jj's first class conflicts solve the issue of having "stacks" of PRs that can easily be updated at any point in the stack? This is one of the features most absent from git, but prevalent in Google's tooling as well as Meta's. The only good known solution I know is graphite.dev

What you are talking about is solved by jjs auto rebase behaviour.

If I amend a commit, all children are rebased automatically.

Re: Jujutsu at Google [video]

#59

Post by martinvonz » Thu, Oct 30, 2025, 9:49 PM UTC

redleader55 wrote: post #40

martinvonz wrote: post #10

Earlier quoted context omitted.

Thanks for the link. I went through it but I'm not sure what it's telling me to change. Can you elaborate? If it's "be more engaging", i think is unfortunately going to be hard to improve because this is just how i am.

I think GP is suggesting using less words on a slide, having visual aids and often, thinking of 2-3 ideas that someone would remember from your presentation. To the first point, if you take more than 1 min on a single slide, you need to split it into more slides. Also, present things that you are passionate about if you want to make people care about your presentation.

Putting less details on the slides is something very actionable. Thanks.

> Also, present things that you are passionate about if you want to make people care about your presentation.

Haha, this topic is something I'm very passionate about. That's how I look when I'm excited :)

Re: Jujutsu at Google [video]

#60

Post by OkayPhysicist » Thu, Oct 30, 2025, 9:51 PM UTC

Cyph0n wrote: post #26

spyspy wrote: post #5

Off topic, and I don't want to knock the presenter here, but if you're ever going to give a public talk or presentation at work _please_ review the Death By Powerpoint slide deck[0] first. [0] https://www.slideshare.net/slideshow/death-by-powerpoint/855...

Good advice for presenting a TEDx talk. Bad advice for a technical talk.

If you don't care about the material, why on earth would anybody sit around for 15 minutes/30 minutes/an hour listening to you talk about the material. The sole reason for a presentation over a technical reference buried somewhere is because the presenter wants the audience to care about the thing they're presenting. If that isn't reflected in the presentation, it's not a worthwhile presentation.