this post was submitted on 28 Aug 2023
131 points (82.9% liked)
Asklemmy
43856 readers
1674 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Use git.
Please.
I'm begging you.
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.
There is always git LFS
It just keeps a copy.
Git is version control
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.
Iβd imagine youβd be hard pressed to find a non-programmer who knows what that is.
I'm not a programmer and I agree. Only after getting into 3d art I started hearing about it and I don't think I've ever used it, let alone understand it, it's the sort of thing the technical artists know about. Nobody ever suggested me to use it for my images or 3d models.
As a visual artist I can confirm the "image_final_final2_b_final" trope is as real as it gets
*nobody until now
Use git
Git is used in other contexts besides programming
Not in many. And usually it happens whenever a programmer does non-programming stuff.
Much less even knows how or why to use it lol