|
|
|
|
|
by dissident_coder
907 days ago
|
|
Unpopular opinion, but I still really like SVN and prefer Mercurial and Fossil to Git as distributed systems. You can install TortoiseSVN for a non-technical user and give them a quick rundown on how to checkout asset files from SVN, how to lock/unlock it when they need it and when they are done and how to commit they can more or less understand it and work with it. GFL getting someone to understand how to use Git LFS or dealing with merge conflicts on asset files. Git's LFS/annexe extensions are serviceable for developers and technical folks but really are subpar compared to a centralized version control options. |
|
I'm one of those weirdos who actually likes git LFS, but only because I admit all it's short comings. But it is working really well for my game dev project. Not what I use to manage my asset library though. It is what I use to sync the most up to date binary files, which is really the use case it is maintained for anyway (think syncing build artifacts or large data sets).