3 ms·

Moreover, even if it was say 15% better than git (and I doubt it is), the overhead of moving a whole industry across VCs is billions of dollars of loss. Every

Moreover, even if it was say 15% better than git (and I doubt it is), the overhead of moving a whole industry across VCs is billions of dollars of loss. Every single engineer has to start over in their mastery experience by learning all the new quirks and issues, and all the tools, libraries, pipelines need to be rewritten. IMO better to support the dominant tooling than invest in fracturing one of the few areas where engineers can agree on something for once (to everyone's benefit).

eviks 2y ago
It's also billions of dollars of gain: every single future engineer won't have to waste time due to 13% worse design. But jj supports git as a backend, so not clear what fracturing you mean, do people using magit front-end fracture?
lawn 2y ago
The upside with jujutsu though is that it's completely compatible with Git and you can work on the same repository with Jujutsu while your coworkers use Git. This allows the people who want the 15% gain to have it, while not forcing anyone to do a costly migration.
- KerrAvon 2y ago
  I know people who really hate git because the UI is so awful, and it’s (theoretically) way more than a 15% gain for them. They’ll get to stop rubbing broken glass against their legs every day.
  - SansGuidon 2y ago
    Git feels like solving puzzles everytime there are branches or collaboration made on a repo. So every day. Most productive days are when I dont need to use git. JJ is a workaround for git pains but the UX is not mature enough for replacing git yet. Having distinct local working copies of same repo per git branch still works great, not stash needed, no conflicts or pain with local wip and drafts changes overwritten by pull. No blocker for switching branches. No reset hard/soft whatever. And makes files comparisons easier and makes my git workflows easier. I still feel vcs could be simpler and solved problem if more engineers care about the topic of vcs and generally speaking about the ux of their main tools instead of creating new TUI and plugins to workaround broken ones.
deleted 2y ago
[deleted]
stouset 2y ago
> Every single engineer has to start over in their mastery experience by learning all the new quirks and issues, and all the tools, libraries, pipelines need to be rewritten. I was a git power user. I became comfortable enough with jj to replace git entirely in one day.
stouset 2y ago
> IMO better to support the dominant tooling than invest in fracturing one of the few areas where engineers can agree on something for once If Linus had this mentality we’d all still be using Subversion.

eviks 2y ago

It's also billions of dollars of gain: every single future engineer won't have to waste time due to 13% worse design. But jj supports git as a backend, so not clear what fracturing you mean, do people using magit front-end fracture?

lawn 2y ago

The upside with jujutsu though is that it's completely compatible with Git and you can work on the same repository with Jujutsu while your coworkers use Git. This allows the people who want the 15% gain to have it, while not forcing anyone to do a costly migration.

KerrAvon 2y ago
I know people who really hate git because the UI is so awful, and it’s (theoretically) way more than a 15% gain for them. They’ll get to stop rubbing broken glass against their legs every day.
- SansGuidon 2y ago
  Git feels like solving puzzles everytime there are branches or collaboration made on a repo. So every day. Most productive days are when I dont need to use git. JJ is a workaround for git pains but the UX is not mature enough for replacing git yet. Having distinct local working copies of same repo per git branch still works great, not stash needed, no conflicts or pain with local wip and drafts changes overwritten by pull. No blocker for switching branches. No reset hard/soft whatever. And makes files comparisons easier and makes my git workflows easier. I still feel vcs could be simpler and solved problem if more engineers care about the topic of vcs and generally speaking about the ux of their main tools instead of creating new TUI and plugins to workaround broken ones.

deleted 2y ago

[deleted]

stouset 2y ago

> Every single engineer has to start over in their mastery experience by learning all the new quirks and issues, and all the tools, libraries, pipelines need to be rewritten. I was a git power user. I became comfortable enough with jj to replace git entirely in one day.

stouset 2y ago

> IMO better to support the dominant tooling than invest in fracturing one of the few areas where engineers can agree on something for once If Linus had this mentality we’d all still be using Subversion.