3 ms·
You can do that, but you will only get some of the features (a distributed backup system with an undo function). The most important one IMO is merging and that
by Lichtso 6y ago
You can do that, but you will only get some of the features (a distributed backup system with an undo function). The most important one IMO is merging and that does not work on arbitrary formats serialized to text. E.g. let two 3D artists fork a blender 3D file in GIT, both do changes and commit them. Until here everything seems fine, now they want to merge their changes ... and suddenly everything falls apart.
Edit: To clarify, if you don't need merging than you also don't need distributed VCS and centralized VCS will be sufficient. That is why I explicitly talked about distributed VCS.
- npsimons 6y agoThis sounds like an intractable problem, and putting it politely, the fault lies in the file format, not the VCS.
- Lichtso 6y agoYou are right, in that it is very hard. That is why I said that I think distributed VCS is far from being solved. However, I think the "fault" lies neither in the VCS nor file format. It simply shows that merging requires domain knowledge and that future VCS will need to cooperate with file formats to achieve that.