> I'm not sure the article explains enough to put git into perspective - its mostly a "what is version control" parable? The parable walks you through git's da

> I'm not sure the article explains enough to put git into perspective - its mostly a "what is version control" parable? The parable walks you through git's data model and is therefore git-centric. The metaphors used are a rather thin veneer on top of the way git actually works instead of a thick and leaky abstraction. You could apply the high-level concepts across other systems but they would not map as cleanly or completely.