Live data from Hacker News

The creator of Jujutsu has joined ERSC

ersc.io

161–170 of 283 posts

Re: The creator of Jujutsu has joined ERSC

#161
post #143

Earlier quoted context omitted.

I was a skeptic until a few months ago. It’s my daily driver now. I’ve got sizable amount of people committing to the same repo, many are not skilled with git. So I deal with weird crazy “how did you ever get the repo into this state” issues not infrequently. JJ is just so low friction. The seamless and painless shuffling of commits, working up and down the commit chain without explicit rebasing, unchanging change-id…

[flagged]

Maybe it's losing steam because it's stable and there's no demand for new features.

Re: The creator of Jujutsu has joined ERSC

#162
post #142

I like the idea of jujutsu, but I must not operate at a scale where its "killer features" would truly shine. Git hardly ever gets in my way, I have never had to do complex octopus merges or anything like that. It's usually: feature branch, implement, merge, and occasionally fix a merge conflict. JJ seems like it's more for people that like to have tons of active branches that they are constantly switching between whe…

I don’t know about you, but if you ever run git commit --amend, git rebase -i, git reset, git reset --hard, git stash, git add ., git push --force-with-lease, then these are all workflows that jujutsu makes easier and less error-prone.

Re: The creator of Jujutsu has joined ERSC

#163
post #44

No word about the future of Jujutsu, so I guess this is bad news for for jj users?

It's in the post, but Martin will be continuing to work on jj itself as well as on our products, just as he did at Google, working on the open source jj but also their internal source control team. As a side note, jj has rules around company representation in maintainership, and so when this initially happened a few months back, ERSC actually became over-represented in the maintainers group, as we also employ several…

That idea about keeping maintainer balance is pretty neat, interesting to see this kind of diligence in maintainership in the same project where legal ownership belongs to a single company, Google, via the Contributor License Agreement. My interest in jj cooled off a lot after seeing that, even though I realize in practice it's pretty unlikely to be of consequence - I just don't need even that kind of low probability Sword of Damocles hanging over my VCS, forks and drama in case Google decides to mess things up. (Good to see that the Readme has been changed to say it's not a Google-supported project btw, less misleading than the old claim that it's not a Google project at all.)

Re: The creator of Jujutsu has joined ERSC

#164

Jujutsu is apparently the name of a version control system, for anyone else confused how the creator of a thousand year old martial art had joined them.

Thanks, I was trying to work it out in my head. I knew brazilian jiu jitsu was 20th century, and I was like "but wait, is jiu jitsu itself not that much older, that seems very surprising."

Yeah. I thought maybe someone from Gracie family joined something :)

Re: The creator of Jujutsu has joined ERSC

#166

Badass!!! Congrats. I love JJ’s mental model. Its so much less opionated and lets me do what I want. Want to make 5 versions of the same commit? Easy. Need to push out a change asap without having to pre create a branch, stash your changes, yadayada. Jj just adapts. Once you start thinking in jj it becomes frustrating having think back to use GitHub as a code repo.

> Want to make 5 versions of the same commit? Easy

When do you need something like this?

Re: The creator of Jujutsu has joined ERSC

#167

Earlier quoted context omitted.

Wasn't it partially owned by Google? Or are they just a contributer now?

I like to compare Google and jj to Mozilla and Rust: Google employed Martin and some other maintainers, but it's always been an OSS project under the Apache 2.0 license. That being said, there's a few things that lead to this perception: the first is that it used to be under Google's GitHub account, but is now under its own org. The second is that contributing to jj does require signing Google's CLA. That is somethin…

Thanks!

Maybe if Martin could comment - his @google.com email still appears in the repo readme, I'm assuming he doesn't have access to that box anymore - was the repo move and ownership coordinated with Google prior to his leaving?

Re: The creator of Jujutsu has joined ERSC

#168
post #69

[flagged]

I left a lengthy comment below about how we'll be supporting git as well. I have been a member of this community for a very long time. Posting here is something I just do. jj is already pretty well known here, there's articles about it quite often. But sure, I don't think that anyone would deny that a VC backed startup posting about their product to Hacker News has marketing value. You have to get the word out someho…

I've met you (Steve) and hung out with him for a few hours after oxidize. He's none of those things, and in fact was one of the most pleasant people I've met at conferences. So not only are they brazen and vulgar allegations but I can't see even a distant parallel universe where they're even close to true.

Super bizarre comment to see on HN.

Re: The creator of Jujutsu has joined ERSC

#169
post #62

Earlier quoted context omitted.

Do you happen to have or know of any good open source projects on any public platform like GitHub, gitlab or Codeberg, that uses Jujutsu/jj?

It's hard to tell since any given dev can just use jj locally, if they want to, while everyone else uses git.

All my prs are named phil- and have been for years now. I keep waiting for someone to care/notice, but no one has.

Re: The creator of Jujutsu has joined ERSC

#170
post #84

Earlier quoted context omitted.

I'd argue that the reason a lot of developers have not learned git in depth is because it's actually kind of terrible from a UX standpoint (lots of inconsistent naming of things and somewhat leaky abstractions), and that Mercurial faced an uphill battle in large part because it lacked compatibility with what people were already using. I haven't used Mercurial, but from what I've heard quite a lot of how jj does thing…

> I'd argue that the reason a lot of developers have not learned git in depth is because it's actually kind of terrible from a UX standpoint Not really. I remember my early years with git and the favt was that I never needed more than clone, add, commit, pull and push. While I’ve done some mistakes that got ne to learn more, especially with creating branches and undoing. I’ve never needed a lot, even when I started u…

But what if you didn’t have to read a 400-page book to properly version control your software?
Post reply on HN