4 ms·
Interesting but this page reads like a marketing piece. The discourse around VCSs is mature and you should BLUF with where yours sits in the spectrum of altern
by 2d8a875f-39a2-4 2y ago
Interesting but this page reads like a marketing piece.
The discourse around VCSs is mature and you should BLUF with where yours sits in the spectrum of alternatives.
What is the repository model and the concurrency model? Those are the basics.
Seems to be centralized & um, merge or lock, maybe? I don't want to have to parse lots of fluff to find that out.
Then, what is the storage method and change scope? How do revision IDs work? No idea and I am not going to dig further.
Final comment is that "100,000 files with 15,000 directories" isn't really that big. How many TB did that represent? How many revisions/branches/history?
- chipdart 2y ago> Interesting but this page reads like a marketing piece. I would go a step beyond and say that the page reads as if it was purposely designed to confuse the reader in order to hide the project's true features and capabilities, and instead create the baseless idea that it solves problems that it can't even state clearly. It reads like it's the zombo.com of VCSs. It's even more perplexing that it tries to portray itself as the next best thing, when it even fails to make a case on whether it even works at all.