3

I know other version control software exists, but does anyone use it? Why? What are the differences? All I've ever actually seen people use is git.

top 10 comments
sorted by: hot top controversial new old
[-] oleid@programming.dev 2 points 2 years ago* (last edited 2 years ago)

There is pijul.

  1. Pijul's defining feature is its innovative algebra of patches model for version control, allowing changes to be applied in any order without creating conflicts, thus simplifying collaborative work.
  2. It efficiently handles branches and merges, with its patch theory often enabling it to automatically resolve conflicts, eliminating much of the headache typically associated with merge conflicts.
  3. Pijul is also free and open-source

Check this out: https://stackoverflow.blog/2023/05/23/for-those-who-just-dont-git-it-ep-573/

[-] BusterLove@programming.dev 1 points 2 years ago

I actually kind of miss Subversion etc now. Git was perfectly designed for open source projects, but its easy branching model has significantly undermined the practice of Continuous Integration in enterprise environments. I get that maybe devs just prefer working in an isolated branch, but something has been lost.

[-] canpolat@programming.dev 1 points 2 years ago

Git is definitely dominating the landscape. The fact that it is free software plays a big role. There are alternatives, but they are unlikely to gain much adoption. They may provide slightly better UX or marginally more comfortable flows, but it's not enough to replace Git. Not to mention, most developers don't even really care about which SCM they use.

[-] sorrus@programming.dev 0 points 2 years ago

There’s perforce which is primarily used for game development. Often games have a lot of binary files that are hard/impossible to generate diffs of unlike text based files. Perforce requires you to check out individual files and prevents any merge conflicts on an individual file basis.

[-] Mikina@programming.dev 1 points 2 years ago

My experience with Perforce hasn't been really positive - especially compared to Plastic SCM, which is amazing. The merge tracking in history is such a cool feature, and it's generally really smooth to work with.

The only issue is the pricing model, which is also a reason why I sadly can't use it on many projects. Unity way too greedy and their strategy is to just acquire and paywall anything usable.

[-] erAck@discuss.tchncs.de 0 points 2 years ago

There is only one alternative for distributed version control, Mercurial. Everything else is significantly inferior, except maybe for special cases. Mercurial may be fine for newcomers to step in, but probably at some point the flexibility of Git will be missed. And because of so many people using Git there are more solutions to specific problems.

[-] oleid@programming.dev 1 points 2 years ago

Everything else is significantly inferior

Which ones did you try?

[-] brunofin@beehaw.org -1 points 2 years ago

I've heard of some corporate environments using different tools because of some weird use case, but honestly I think it doesn't justify, if you're taking it seriously you should be using git.

[-] Netrunner@programming.dev -2 points 2 years ago* (last edited 2 years ago)

Git is freaking amazing. Any current alternative is going to be a joke next to it.

People using other ones are simply missing out. SVN/CVS just need to die.

[-] jim@programming.dev 1 points 2 years ago

I've heard good things about hg though I haven't used it myself. Git has the biggest mindshare that I never bothered even checking. Might as well use it and move on.

this post was submitted on 02 Jul 2023
3 points (100.0% liked)

Ask Experienced Devs

1232 readers
1 users here now

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago
MODERATORS