Re:What’s wrong with Git? A conceptual design analysis (2016)
by jayd16 on Tuesday April 27, 2021 @11:23PM
(#26965183)
Git LFS is really robust these days. Personally I think its faster then Perforce now. Reconciles can hang and there's just so much more that can be done in git without hitting the network.
GitLFS supports locking too.
Re:What’s wrong with Git? A conceptual design analysis (2016)
by traviscj on Tuesday April 27, 2021 @10:43PM
(#26964886)
I really love the pragmatism behind saying: yes, X sucks, but it’s still useful.
Re:What’s wrong with Git? A conceptual design analysis (2016)
by m463 on Wednesday April 28, 2021 @12:49AM
(#26965715)
I like that a changelist is one atomic unit in time across everything. Don't underestimate the number of footshoots this avoids. and you can build your tooling on top of it.
Re:What’s wrong with Git? A conceptual design analysis (2016)
by satya71 on Tuesday April 27, 2021 @10:34PM
(#26964813)
Perforce has a product called Helix4Git, which apparently allows you to use Git with Perforce. Is it something you tried?
- Large binary asset support.
- Exclusive locks for binary assets.
- Speed. When configured properly, it's very fast, particularly for large repositories.
- Tooling support. It's nearly ubiquitous in gaming.
I'm working on repositories that are 100+ GB and need to support both programmers and artists. Git just isn't the right tool.
We do use git for backend server-side projects. Having to support two different version control systems is a pain, but, again, it's useful to have the right tool for the job.