The integration of Git LFS has a lot of advantages.
As you’ve said, strip out binary data from repository and putting them into LFS reduces the size of repository a lot, but it’s not only it. For example when you clone the repo, you clone only the little repository, and then download only the necessary binary data, instead of downloading the entire binary history, so also inside your pc the size of the repo is smaller.
In addition to this, Git LFS adds git commands for working better with binary files, like the locking. This reduces a lot the problems when working with those data, for example because usually they cannot be merged, so the lock is necessary then one is updating the file, and this avoid concurrent changes that cannot be solved by a normal merge, things that’s instead possible with text.
So yes, Git LFS is worth it because is specifically designed to overcome the most common and annoying problems that overcome when using git with repository with binary assets, and it became a valid alternative to perforce.
It’s worth paying it, but if you don’t want to, you can use Azure Devops since for personal projects you don’t have space limits for Git lfs.
1 Like