senekor

5 ms·

1.
Flirt: The Native Backend(blog.buenzli.dev)
34 points by senekor 8mo ago|15 comments
2.
by senekor 11mo ago
That's also my opinion, that jj should be easier for juniors to pick up. However, I felt like there's a lack of learning material targeted at people without prior VCS experience. That's why I wrote "Jujutsu for everyone&
3.
Announcing Development on Flirt(blog.buenzli.dev)
4 points by senekor 11mo ago|2 comments
4.
by senekor 1y ago
Yes and no. Before I started using Jujutsu, I didn't have any pain points with using Git. I didn't understand what all the fuss was about. Git works well! So I totally understand how most Git users have that same reaction when hea
5.
by senekor 1y ago
I mean, it certainly is that, but not only that. Jujutsu has more to offer than a consistently designed CLI. You can't do non-blocking merge/rebase conflicts with Git aliases. You can't do `jj absorb` with Git aliases. And yo
6.
by senekor 1y ago
Thanks, but I consider myself a Git expert already :-) I read the Pro Git book cover to cover. I have a gluten-free, artisanal, free-range git config that I've grown and cared for over years. single character aliases all the important
7.
by senekor 1y ago
Just a few tips: > - i'm forced to be "strict" with my changeset since there's no `git add -P` Check out the command `jj split` and possibly `jj squash --interactive`. > - bookmarks are a pain to keep up-to-date wi
8.
by senekor 1y ago
> I'm having a hard time wrapping my mind around what specific details would cause me to choose Jujutsu over Git, in particular because of Git's industry standard status. Jujutsu is Git-compatible, so there's nothing to lo
9.
by senekor 1y ago
Hi, author here. Since the target audience is people with little to no Git experience, a detailed comparison would not make sense. I did simply make that claim because the weirdness of Git's UI is usually justified by saying how powerf