Live data from Hacker News

The creator of Jujutsu has joined ERSC

ersc.io

61–70 of 283 posts

Re: The creator of Jujutsu has joined ERSC

#61

Earlier quoted context omitted.

It's killing my GPU tho so can't look at it took long without my fans going to max.

What is your browser/OS combo? Thank you for bringing it up, we can only fix things that we hear about, so I appreciate knowing that something is off.

No worries, Windows 11, browser I just tested in Opera and Edge. Shared Intel GPU runs at 70% in either, guessing due to the lovely clouds drifting by.

Re: The creator of Jujutsu has joined ERSC

#62
post #55

Working with Martin has been a real pleasure, and we'll have some more stuff to talk about very soon!

I absolutely love jj (just check my HN comment history). One thing I'd love to see in jj though that git does better is copy tracking. If somebody renames a file upstream, and you go to rebase your commit that touches that file onto main, jj doesn't handle this very well compared to git. Do you have any idea if this is coming to jj soon?

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?

Re: The creator of Jujutsu has joined ERSC

#63
post #35

jj is one of the few new devtools I was quite frustrated with while starting out but could see the value so stuck around and man is it so nice. For anyone curious the big thing with jj is you can undo. Basically if you were running a rebase and bungled a commit sha or branch name, no worries undo your way out, if you forgot to push but abandoned a commit not issues undo it. Same with all jj commands. Delta db takes t…

A term coined within Google that describes the best part (to me at least) of jj: delayed conflict resolution.

You worked on multiple things, you sync with the upstream, then boom now you have conflicts in one or more of your local branches.

Instead of immediately presenting you a conflict resolution view (usually 3 pane vimdiff) and you'll have to resolve at the sync time, the commits are simply marked as "have conflict", and you can continue working on other things until you have time to deal with it.

And for a chain of commits that all have conflicts, chances are fixing the first conflict automatically resolves all other conflicts in the chain, thanks to the auto-rebasing feature.

Re: The creator of Jujutsu has joined ERSC

#64

Earlier quoted context omitted.

We'll be saying more about this very soon, but the short version is this: we are not building a GitHub competitor in the way that SourceHut or Codeberg are. We are building infrastructure for enterprises, not a social coding site. While jj works with git, it doesn't have to. jj has the ability to work with many backends. Git is the popular one in the open source world, but that doesn't mean that other ones are not po…

Are you guys hiring? (Software Engineer that writes in Rust.)

We are not actively hiring at the moment, but will be in the future for sure.

Re: The creator of Jujutsu has joined ERSC

#65
post #17

Jujutsu is a better smarter git. It's a great convergence of better UX, plus more expressive, plus easier to use. If you haven't tried jj yet, take it for a spin and see how you like it.

How does it compare to Mercurial? And why would it get more traction than Mercurial?

Re: The creator of Jujutsu has joined ERSC

#66
post #63
post #35

jj is one of the few new devtools I was quite frustrated with while starting out but could see the value so stuck around and man is it so nice. For anyone curious the big thing with jj is you can undo. Basically if you were running a rebase and bungled a commit sha or branch name, no worries undo your way out, if you forgot to push but abandoned a commit not issues undo it. Same with all jj commands. Delta db takes t…

A term coined within Google that describes the best part (to me at least) of jj: delayed conflict resolution. You worked on multiple things, you sync with the upstream, then boom now you have conflicts in one or more of your local branches. Instead of immediately presenting you a conflict resolution view (usually 3 pane vimdiff) and you'll have to resolve at the sync time, the commits are simply marked as "have confl…

> And for a chain of commits that all have conflicts, chances are fixing the first conflict automatically resolves all other conflicts in the chain, thanks to the auto-rebasing feature.

What happens if one is unlucky and the conflicts are not automatically resolved from changes to the first commit? Does that potentially imply more work overall than if one was using a VCS that forced conflict resolution earlier, like git?

Re: The creator of Jujutsu has joined ERSC

#67
post #65
post #17

Jujutsu is a better smarter git. It's a great convergence of better UX, plus more expressive, plus easier to use. If you haven't tried jj yet, take it for a spin and see how you like it.

How does it compare to Mercurial? And why would it get more traction than Mercurial?

Mercurial is too slow. Even with chg common commands like `hg status` may take hundreds of milliseconds. JJ is fast. Internally `jj log` taking more than 500ms is tracked as bugs.

Re: The creator of Jujutsu has joined ERSC

#68

Earlier quoted context omitted.

The enterprise sounds accurate. You mention performance issues with Git, but there are performance issues with this blog post.

What is your browser/OS combo? I am assuming it's the animation, we tested it thoroughly but there can always be bugs. Thank you for bringing it up!

Windows, Chrome, fans spin, recommend ai review

Re: The creator of Jujutsu has joined ERSC

#70

Earlier quoted context omitted.

Are you guys hiring? (Software Engineer that writes in Rust.)

We are not actively hiring at the moment, but will be in the future for sure.

Post to the HN Who’s Hiring threads when you do :D
Post reply on HN