Idk, but not anything that uses delta compression like git does.
Game developers use Perforce and Plastic scm which is (supposedly) optimized for images and other binary assets. I’ve never used them, but I’m sure a less-overkill and open source alternative exists somewhere.
That's the thing, everything that I could find is a huge project made for storing huge projects, costs a lot of money and requires effort to install and even use. Yeah, naked git basically stores new version of an image for every commit, but nothing beats the fact that you need like two commands to use it and it just works, and storage is very cheap this days. And if you add LFS, it even does some kind of storage compression.
For image files? I know you can save image files and git but I just don't know what it does with them.
Don’t use git for images (or most other binary data)
It's still way better than _final_fixed(2) version control.
What do you propose to use as a version control for images?
Idk, but not anything that uses delta compression like git does.
Game developers use Perforce and Plastic scm which is (supposedly) optimized for images and other binary assets. I’ve never used them, but I’m sure a less-overkill and open source alternative exists somewhere.
That's the thing, everything that I could find is a huge project made for storing huge projects, costs a lot of money and requires effort to install and even use. Yeah, naked git basically stores new version of an image for every commit, but nothing beats the fact that you need like two commands to use it and it just works, and storage is very cheap this days. And if you add LFS, it even does some kind of storage compression.
Git is version control
It just keeps a copy.
from what I remember, Git is just a file system under the hood. So it would just end up saving a copy of each image under the hood.