3 ms·
Not really a new idea to use a VCS as a document database, other folks have back-ended Wikis and document management systems with SVN, for example. But a nice
by ams6110 18y ago
Not really a new idea to use a VCS as a document database, other folks have back-ended Wikis and document management systems with SVN, for example. But a nice story regardless, and another nudge for me to really take a closer look at git.
First distributed VCS I heard of was darcs. I have not used it either, but from what I've read about the two, git has some real advantages in speed and robust-ness.
- igorgue 18y agoDarcs is just different, also when this Git buzz started the Darcs people were wondering why they didn't just contribute to Darcs since their ideas are almost the same (except for some things like the merge algorithm)... they just realized that some people just don't program in Haskell :(
- mbrubeck 18y agoGit and Darcs have very different underlying models. Most importantly, Git is content-centric (diffs are generated only as byproducts) while Darcs is patch-centric (any given "version" is just a sum of all the patches that produce it). Linus, for one, feels strongly that this is an important distinction.
- davidmathers 18y agoNot really a new idea to use a VCS as a document database, other folks have back-ended Wikis and document management systems with SVN, for example. It's not the same thing. Using SVN as a document database is equivalent to using the filesystem as a document database. The only thing extra you get with SVN is a revision history. Git actually is a content database. Its version control capabilities are built on top of that. When you do a checkout on a traditional VCS you're telling the VCS to apply patch set x to the file system. When you do a git checkout you're telling git to load content x from the database into the filesystem.