Thread #108611066
File: 1772779369881901.png (155.8 KB)
155.8 KB PNG
Anybody migrate personally or professionally to using jujutsu/jj over git? Thoughts? It's the latest and greatest version control system https://github.com/jj-vcs/jj
26 RepliesView Thread
>>
>>
>>
>>
>>108611066
>https://github.com/jj-vcs/jj
>open repo
>.cargo
fucking dropped, no wonder the logo is two peckers touching each other
>>
>>
>>
>>108611066
i see no point in using something that replicates git. I learned git and it works. Why would I waste time learning same shit as different commands and confuse myself while inevitably having to work with tegular git. Even if whole industry magically adopted it, the migration would take decades and you would have the problem of shuffling both and being annoyed. It won't replace git. If upu want an alternative, write something that actually works differently. As for git, you can just use aliases and source control them.
>>
>>
>>
>>108611066
>Working-copy-as-a-commit: Changes to files are recorded automatically as normal commits, and amended on every subsequent change. This "snapshot" design simplifies the user-facing data model (commits are the only visible object), simplifies internal algorithms, and completely subsumes features like Git's stashes or the index/staging-area.
Sounds like complete garbage. How am I supposed to split changes into multiple discrete commits? The git index is useful. This jj thing does away with it because they're too dumb to understand it I guess.
>>
>>108611950
>>108611681
You got a problem with blue jays?
>>
>>108611422
no
they have plans to have a different backing store later
but they’re using Git for now
t. never used jj
>>108611993
this
>>
File: noided.jpg (14.8 KB)
14.8 KB JPG
>>108611066
GIT GIT GIT GIT GOT GOT GOT GOT
https://gameoftrees.org/index.html
>>
>>108611066
My gut reaction is that I hate it. My more considered reaction after reading a bit more about it is that I still hate it. It looks like a bizarre layer on top of git that makes it worse in every way.
I wonder how much of that reaction is reasonable, and how much of that is just my brain starting to fossilise and becoming afraid of new systems and techniques.
>>
>>
many arguments i've read online about what makes it great is that it's supposedly easier to learn than git.
assuming this is true, good for them, but that also means there is no incentive for me to switch besides maybe altruism so I can teach other people version control more easily
>>
It sounds briefly tempting but in a practical context, it just sounds like a pitfall-laden attempt to make Git more usable, since everyone will end up using Git as the backend anyhow. I already have Magit for that.
It doesn't help that the tutorial is ridden with redditspeak.
>>
>>108611993
>How am I supposed to split changes into multiple discrete commits?
You can still do that
> The git index is useful
Point of jj is that you can achieve the same flexibility without exposing the index
jj is just unarguably plain better than git . Git not having undo and conflict as fist class concept is just retarded
>>
File: jj-split.png (91.5 KB)
91.5 KB PNG
>>108611993
>How am I supposed to split changes into multiple discrete commits?
>>
>>
>>
>>
>>
>>
>>108620127
it sounds like the same reasoning that brought us the LaTeX retardation
Fighting the vcs should be the last thing you should put your effort to when building sw. Jujustsu achieves the same flexibility of git without the all its warts (exposing the index, not having undo, the existence of stash is a clear symptom they fucked up the change model, UX that is utter garbage, etc...)
The credit that must be given to git is that they managed to get people to adapt to Git’s unnatural model to the point of genuinely convincing themselves that it is the best way to implement a vcs