Maybe a mixed approach similar to what dvc [0] is doing. Fully integrated with git but tracked and stored elsewhere.

[0] https://dvc.org/

Programmers, game makers and 2D/3D artists are very different target audiences with very different needs. To name one example, the commit hash integrity which is a foundation of Git is a must-have for software projects, but might be not useful in environments like VFX or CG productions

Also, the project is very clear that it is for individuals with no collaboration tools built in. While git does have utility for a solo developer, having a separate system for a solo artist (that isn’t working with assets for developers), starts make more sense.

> Programmers, game makers and 2D/3D artists are very different target audiences with very different needs.

Yes, so if you want to make them use the same version control system (not a strange requirement, see Google monorepo), then the system should be all-encompassing, and not limited to one type of user.

And it may turn out that features meant for one type of user are also useful for other types of user. For example, programmers may need to store large image files as part of a deep-learning image classification system.

I'm usually not a fan of packing as many features as possible into a single tool, but in case of version control it makes sense. (A pluggable/modularized approach should of course be used if possible).

You are absolutely right! A tool that can cover everyones needs is a great goal, and a pluggable or modularized approach might be even the best. SnowFS is not a one-way street, there are certain features that are currently investigated to be feature-proposed for libgit2. Means, this project is a great way to explore the possibilities without any historical or technical barriers because it is so lightweight. Best proof are the benchmarks

AFAIK big studios use perforce.

Most productions I've seen Perforce is still the way to go, sometimes PlasticSCM for Unity