Programming

22723 readers

234 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

176

Let's Make Sure Github Doesn't Become the only Option - Edward Loveall (blog.edwardloveall.com)

submitted 1 day ago by mesamunefire@piefed.social to c/programming@programming.dev

34 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] IanTwenty@lemmy.world 2 points 1 day ago (2 children)

Jujutsu is another git alternative I keep seeing around and came to mind reading this:

https://steveklabnik.github.io/jujutsu-tutorial/introduction/what-is-jj-and-why-should-i-care.html

[–] thenextguy@lemmy.world 22 points 1 day ago (3 children)

Why? This is isn't about git. It's about github. Two completely different tools.

[–] SorteKanin@feddit.dk 1 points 12 hours ago (1 children)

Did you read the post? The author suggests trying out other version control systems too.

[–] thenextguy@lemmy.world 1 points 8 hours ago

Yes. I thought it was poorly written.

[–] IanTwenty@lemmy.world 5 points 1 day ago

I know. The author suggests:

Experiment with new-to-you version control systems like Fossil, Mercurial, and Pijul.

The author is:

learning about different version control systems. For example, the differences between Fossil and git revealed a lot of my biases towards git simply because it’s familiar (and Fossil seems really cool). Reading about the theory behind Pijul absolutely bends my brain into knots. I keep trying anyway because conflicts in git are frustrating and I’d like a better solution.

The author says:

It would be nice to move beyond git one day and have a better experience for managing complex codebases, and not on GitHub’s timeline.

[–] limer@lemmy.ml 2 points 1 day ago (1 children)

I think it’s valid unless one thinks git should be the only standard. Looking at other tool chains opens options

[–] Ephera@lemmy.ml 9 points 1 day ago (2 children)

Jujutsu is a Git frontend, from what I understand, much like there's tons of Git GUIs. So, you interact with it in a different way, but you still push to a Git repository and others can interact with your code by using Git.

I guess, it somewhat lessens the grip of Git, because they can hook different backend services (e.g. Subversion, Mercurial, Fossil) into this frontend, and from what I understand, they plan to develop an own backend eventually. But yeah, for now, the communication standard is still Git.

[–] anti_antidote@lemmy.zip 2 points 19 hours ago

It's not a Git frontend per se, it just uses Git as a storage layer (Google's internal backend doesn't use Git and behaves more like a commit cloud)

[–] KissYagni@programming.dev 3 points 1 day ago

I gave a try to jj. It's fine for personal projects or small team and make the workflow a bit easier. No more "git add; git commit; git push" each time you do a modification. You just "jj git push" and everything will be automatically pushed.

However, the biggest criticism I have is that he doesn't encourage to push every time. It really encourages you to keep your modif locally and push only to create a PR, and that's not a good approach.

Even if you code is WIP, even if everything crash, you really should push your code to backup it. Who cares ? As long as it is not on master branch, it's your own mess.