- cross-posted to:
- opensource@lemmy.ml
- cross-posted to:
- opensource@lemmy.ml
You must log in or register to comment.
The project description reminded me of a project I saw years ago. I looked it up, and I’m pretty sure it was oxen, which is surprisingly still going, although their hub looks half-dead.
I was trying to figure out it’s use-cases
Lore is a next-generation open source version control system maintained by Epic Games. Designed for unprecedented scalability—both in terms of data size and the size and distribution of teams and repositories—it is especially optimized for projects that combine code with large binary assets, such as those found in the games and entertainment industries.
Oh yeah this is solving a huge problem. Games struggle with versioning because of the limits in place of git.
This would also be good for MCAD maybe? It also has a ton of binary blobs often from git’s perspective.
I didn’t know about git LFS (which doesn’t record the history of the files IIRC, just gives a pointer to larger bucket storage), so one of my projects ballooned to 1.2GB and took a lot of time to sync and then doubled when I tried to move to LFS and delete the history of those files, but at least it is fast as hell to push and pull now.
Why is the Lore codebase itself five git repositories, not five Lore repositories?
I imagine because it’s not a game, so git has no problems
Because github doesn’t support Lore (yet)
This won’t gain traction no matter how good it is because it isn’t git.
It’s specifically for the kinds of things git is bad at. Try running a large unity project with git and you’ll feel the pain, it works, but not well and with lots of struggle along the way. I’m not smack talking git here, it’s just that git wasn’t designed for that kind of thing.
Git LFS is a thing. I’m not denying if it’s good. Git is just, ubiquitous.
Git LFS feels like a pretty big band aid and adds a bunch of cost of you are using any service
most large game studios use perforce.
Yep, was just gonna say this.