At this point I’m very concerned about the open source industry relying so much on github. You have to remember that any project there can be swept away overnight because it doesn’t fit into the agenca of a large company, for example.
At this point I’m very concerned about the open source industry relying so much on github. You have to remember that any project there can be swept away overnight because it doesn’t fit into the agenca of a large company, for example.
Not sure what you mean. My understanding is that git itself is decentralized insofar as each clone can develop its own history without ever needing to push to the origin, but that what OP is referring to is actually the “distributed” nature of git, where i.e. it’s easy to copy the entire history of an instance.
Exactly. Isn’t decentralized itself since it’s not a platform but by being “indipendent” and not entangled with anything you can just copy it entirely and host it somewhere else.
I think I see your definition of “decentralized” a little better now, if you only want to apply it to platforms.
I think your definition may be too strict, and that “decentralized” and “distributed don’t have to be mutually exclusive, but eh, that’s just my take.
Git being snapshot-based unlike other (better) VCSs require that patch order matter so often the easiest way to manage a project is to have some centralized authority since it is so, so easy to get merge conflicts without a central authority if trying to just distribute patches. It’s a lot easier to be decentralized without Git’s fundamental limitations.
What version control software in particular do you find better than git?
Your point about users often managing git projects via centralization is taken and valid. I was just pointing out that you don’t have to use git that way - different clones can separately develop their own features - so the earlier claim someone made that “git isn’t decentralized” is still wrong, imo.
Git is distributed but still centralized. D in DVCS is distributed. Downvoters likely have never used a non-Git VCS, let alone a non-snapshot-based VCS. But fanboys will fanboy.
Pijul & Darcs are based on Patch Theory which make the conflicts of different patch order a non-issue so long as the apply cleanly (such as working on different ports of the code base). Patch A then patch B ≡ patch B then patch A; this will be a needless merge conflict in Git since the order matters. (& no, Jujutsu isn’t the solution still shackled to the limitations of Git as a back-end while claiming to do what Pijul does—but doesn’t).
How can I subscribe to the answer?
Darcs & Pijul are based on Patch Theory. https://darcs.net/Theory