Can I throw this back the other way? The first question should be: What is it, and why, that makes git work so well for source code? Even very large code bases?
By questioning (and understanding) the opposite, you get a better feel for the key aspects of the successful system, no matter what system you are looking at. [One is not in control of a system unless one can stop it : A system engineer's aphorism] On 27/05/2020 20:28, David Genest wrote: > Hi, > > With the adoption of Git by the Windows code base and internally at > Google, these giants have invested upstream in better support for > large files in the partial-clone feature. > > Is it time to reconsider git for binary assets like textures and sound > files? Can I `git add [large file]` without second questioning what > I'm doing? > > The perceived applicability of Git for large files is that it is not > the right tool for that job. Does partial-clone remove this limitation? > > If not, when should we think this will become a reality? > > Thanks! > > David. So is it binary assets (what does that really mean...) that are a key feature... Or is it 'large files' (what's large? (and will it stay that way- my first computer had 8 x 1kbit ram / card!) as the killer feature. What is the sneak route aspect of partial clones that make it useful? Ultimately; was any of that the killer feature of Git? I have deliberately avoided an 'answer' because it would be too locked into my perceptions about those questions. A pause for thought. Philip. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/54005bd1-9e57-6886-3bdb-1ead5f79c739%40iee.email.
