61–70 of 120 posts
It's my first time encountering your writing Steve, loved it! Time to give JJ another crack...
thank you steve, i’ve been excited for this!
I really like Jujutsu but I went back to Git because there wasn't a Neovim plugin with features comparable to Neogit or Fugitive. I even started writing one but that was a pretty big project and I lost the motivation for it.
Earlier quoted context omitted.
Interesting. I'm not a professional developer and also love fossil for toy/hobby projects. I find it fascinating that this well crafted, solid piece of software is so forgotten, and that git has just rolled over everything.
Honestly you could sell me the best alternative to Git that exists and I still wouldn’t switch, or even try it. I don’t care enough about my versioning system to use something else than what everybody uses. Ubiquity beats convenience. What I care about is the tooling around it: GitHub and its ecosystem mainly. I also want my open source projects to be on GitHub specifically, and I don’t want to ask contributors to us…
Earlier quoted context omitted.
Honestly you could sell me the best alternative to Git that exists and I still wouldn’t switch, or even try it. I don’t care enough about my versioning system to use something else than what everybody uses. Ubiquity beats convenience. What I care about is the tooling around it: GitHub and its ecosystem mainly. I also want my open source projects to be on GitHub specifically, and I don’t want to ask contributors to us…
Totally respect you wanting to not care about tools, but for the latter part, I do agree with you, which is why I like jj: it uses a git repo as its backing store, so your projects can live on GitHub and all the rest of your collaborators can use git. Nobody else needs to know or care.
Well, guess I’m on my way to read the tutorial.
Earlier quoted context omitted.
Totally respect you wanting to not care about tools, but for the latter part, I do agree with you, which is why I like jj: it uses a git repo as its backing store, so your projects can live on GitHub and all the rest of your collaborators can use git. Nobody else needs to know or care.
Wow I’ve heard about jj multiple times before but didn’t realize it was compatible with Git. You got me interested in just 1 sentence, nicely done! Well, guess I’m on my way to read the tutorial.
Would be great if it was Pijul that got Steve's attention. Sometimes it's all you need to achieve a lot.
I’ll just be honest with you: Pijul never really caught my interest, but I always felt pretty neutral about it until I started noticing the project authors acting very snide and aggressive on here. That is not something I want to be around these days, and so I doubt I’ll ever try Pijul.
What caught my interest:
* Separate operations and data
* Partial repos = no big repo issues, no need for shallow clones and such
* Proper and easy merging with no shuffled lines
* Patch-based model is much more intuitive (e.g. rebase and merge are the same operation)
* Conflict resolutions are stored and can be reapplied!
> I also heard friends rave about "stacked diffs" but struggled to understand what exactly was going on there. Nothing I read or conversations I had have clicked. I wonder what it is about descriptions of stacked diffs that doesn't land - it's literally just a rebase-centric workflow instead of the merge-centric workflow popularised by GitHub et al.
For me, my git brain is very low level. And none of them ever explains what actually happens under the hood, or how that was different than branching… With some respect, I think “rebase centric workflow” doesn’t really cover it: I use rebasing heavily with GitHub. A “trunk based development where all branches are rebased before merge so there’s never merge commits, please add to commits and rebase the branches in res…
Git and Github do not support this workflow directly, and this creates space for all the other tools.
Jujutsu comes close to supporting this workflow directly, without having to provide any specialized utilities that mention "stacked diffs" at all.
https://github.com/spacedentist/spr (not to be confused with ejoffe/spr) is a utility that maps a local change to a remote branch, updating the branch (without force pushes) when the local change is updated. (Changes work the same as they do in JJ, but the implementation is different.) And this works even when you have a stack of changes and update one in the middle of the stack.
I get that naming is one of the hardest problems in computer science, but naming software after a martial art is just lazy and will lead to problems with things like searches
> The command-line tool is called jj for now because it's easy to type and easy to replace (rare in English). The project is called "Jujutsu" because it matches "jj".