So I fully agree with you, but one area for more artist heavy workflows where git still struggles is ease of use.
The two biggest issues are:
- git lfs doesn't automatically identify large files or binary files. So it's very easy for even experienced engineers to have set up lfs but forgotten to track a file or extension
- git exposes too much of its internals. It's really cumbersome for artists even with UI tools.
That's not to fault git as a technology but I think there's a place for an artist friendly layer on top of git, perhaps a very artist centric UI and set of tools and workflow guides
Comments
So I fully agree with you, but one area for more artist heavy workflows where git still struggles is ease of use.
The two biggest issues are: - git lfs doesn't automatically identify large files or binary files. So it's very easy for even experienced engineers to have set up lfs but forgotten to track a file or extension
- git exposes too much of its internals. It's really cumbersome for artists even with UI tools.
That's not to fault git as a technology but I think there's a place for an artist friendly layer on top of git, perhaps a very artist centric UI and set of tools and workflow guides