Epic Games announced today they have created a new version control system that is now open-source as Lore. Given the proliferation and excellence of Git, you may be wondering why Epic Games is pursuing another VCS option... They are specifically catering Lore to games and entertainment purposes with large file sizes.
While there is Git LFS for large file storage with Git, Epic Games has crated Lore as a version control system designed entirely around the large file needs of modern game development as well as multimedia/entertainment purposes. Lore is designed to be fast and efficient for large files including binary files, and be easy-to-use including for 3D artists and more.
Having used cvs and svn in a professional context, I absolutely love git. The cli took a little while to learn, but now all of my common workflow, troubleshooting, and branch/history hygiene...
Having used cvs and svn in a professional context, I absolutely love git. The cli took a little while to learn, but now all of my common workflow, troubleshooting, and branch/history hygiene commands are muscle memory. Throw in a few custom aliases for convenience and I’m good to go. The only time I leave the official git cli is to use IntelliJ’s conflict resolution GUI for complicated conflicts (the “magic” resolve gets me 90% of the way there, and I’m already using IntelliJ as my primary IDE, so it’s right there); I still commit after resolving and do everything else with the cli.
The only thing bad about git is that people centralised in using GitHub as a common source repository hosting platform, antithetical to the idea of a decentralised VCS. But that's just what people...
The only thing bad about git is that people centralised in using GitHub as a common source repository hosting platform, antithetical to the idea of a decentralised VCS.
But that's just what people do: we trade some functionality for convenience.
(there's probably more bad things about git, but...)
It's not really an alternative to git. Git is purpose built for repos of syntactically meaningful text; this is meant for source control of binaries. If anything it's an alternative to perforce.
It's not really an alternative to git. Git is purpose built for repos of syntactically meaningful text; this is meant for source control of binaries.
I was wondering if they built merging for binary files: [source] Not super interesting without that IMO. I'm imagining merging .psd files by layer/effect/etc. or meshes by disjoint segments (ex:...
I was wondering if they built merging for binary files:
More advanced capabilities — such as partial binary merges exploiting Lore's fragment-level storage, and pluggable custom resolvers by content type — are part of the longer-term roadmap.
Not super interesting without that IMO. I'm imagining merging .psd files by layer/effect/etc. or meshes by disjoint segments (ex: you work on the stock of the gun I'll finish the barrel). They do however have a classic "check out" system where the server locks a file someone has made a temporary claim to.
The more alternatives to the horrid git, the better,
Having used cvs and svn in a professional context, I absolutely love git. The cli took a little while to learn, but now all of my common workflow, troubleshooting, and branch/history hygiene commands are muscle memory. Throw in a few custom aliases for convenience and I’m good to go. The only time I leave the official git cli is to use IntelliJ’s conflict resolution GUI for complicated conflicts (the “magic” resolve gets me 90% of the way there, and I’m already using IntelliJ as my primary IDE, so it’s right there); I still commit after resolving and do everything else with the cli.
The only thing bad about git is that people centralised in using GitHub as a common source repository hosting platform, antithetical to the idea of a decentralised VCS.
But that's just what people do: we trade some functionality for convenience.
(there's probably more bad things about git, but...)
Why do you think git is horrid?
It's not really an alternative to git. Git is purpose built for repos of syntactically meaningful text; this is meant for source control of binaries.
If anything it's an alternative to perforce.
I was wondering if they built merging for binary files:
[source]
Not super interesting without that IMO. I'm imagining merging .psd files by layer/effect/etc. or meshes by disjoint segments (ex: you work on the stock of the gun I'll finish the barrel). They do however have a classic "check out" system where the server locks a file someone has made a temporary claim to.