| Maybe the better question to ask is "why isn't file reversion control adopted more outside of software engineer?" Git a is distributed version control system that most people shouldn't have to deal with. It has awful tools and doesn't work well with binary files, large files and moved files.
Just an example: How do you diff two copies of an excel document with Git? Most people don't have to deal with multiple "master" branches with no single source of truth because that's really what Git is for. What most people need, including software engineers working in closed source, is a single source of truth with good history, diff and large files support. I believe a tool like Dropbox or even centralized version control systems like Subversion or Perforce are better positioned to solve this than Git. Many cloud based tools already have features that give them the upper hand over git. For example, Google docs allows collaborative editing and editors have access to file history and can revert to specific versions. Maybe there are tools to diff binary files like two versions of an audio file or two excel documents or whatever two [domain specific file format] documents. I will be happy if version control came at the file system or cloud drive level and the app just leveraged this integration seamlessly instead of forcing everyone to learn the difference between between branching, rebasing, cloning, copying, stashing, etc... |