3 ms·

Not handling large binary files is a feature from my perspective. Git is for source code and treating it like a disk or a catch all for your project is how peop

Not handling large binary files is a feature from my perspective. Git is for source code and treating it like a disk or a catch all for your project is how people get into scaling trouble. I don't see any reason why versioned artifacts can't be attached to a build, or better, in a warm cache. I get that it's easier to keep everything together, but we can look at the roots of git and it becomes fairly obvious, Linus wasn't checking in 48GB 4K mpeg files for his next FPS.

maccard 5y ago
> I don't see any reason why versioned artifacts can't be attached to a build, or better, in a warm cache Because now you've got two versioning systems with different quirks and tools that behave slightly different that _must_ be kept in sync. > I get that it's easier to keep everything together, Easier is a bit of an understatement. Putting binary files outside of the project in another versioning system means you need two version control systems, _plus_ custom tooling to glue the two together. Also, the people who interact with these assets primarily are not technical at all, they're artists or designers, and they're the most likely to have issues with falling between the cracks.