News for hackers. Stuff that matters.
Re:Why SQLite Does Not Use Git by hprotagonist on Saturday July 22, 2023 @10:01PM (#36831899)
> The D is DVCS is a waste of effort.

until the de facto centralized remote goes offline and you’re stuck with no local history …

Re:Why SQLite Does Not Use Git by kstrauser on Saturday July 22, 2023 @10:08PM (#36831936)
Or on a plane. It’s nice to have 100% of its functionality when you have 0% of your usual connectivity. Branches, commits, merges, all from the local file system? Yes, please.

There’s a reason we moved off centralized VCS en masse.

Re:Why SQLite Does Not Use Git by forrestthewoods on Saturday July 22, 2023 @10:39PM (#36832086)
Sorry, but you’re completely and objectively wrong. This is a huge misnomer.

Distributed and “offline support” are fully orthogonal features.

Distributed means every user has a full copy of the entire repo including full history. This is a radical and unnecessary limitation on the scope and size of source control.

You can have full support for branching, commits, and merges without a fully distributed repo. There are numerous examples of this.

Re:Why SQLite Does Not Use Git by yjftsjthsd-h on Saturday July 22, 2023 @11:37PM (#36832357)
> Distributed means every user has a full copy of the entire repo including full history.

Then git must not be a DVCS; I use shallow clones all the time.

In any event, centralized systems probably can do offline support, at least in theory, but DVCSs more or less include it for free by default, which is still worth something.

Re:Why SQLite Does Not Use Git by kstrauser on Sunday July 23, 2023 @01:03AM (#36832684)
That's an interesting, and wrong, definition of "wrong".

Git, Mercurial, and the like make every full copy of the repo equal. By convention, we often use central repos like GitHub, and commands like "git fetch" and "git push" as fast ways to sync their contents. We don't have to, though.

I can clone a remote repo, then work independently for months. I do this all the time with the Mastodon server I run. I periodically pull in upstream changes, merge them into my working copy, then push those changes out to my worker instances. I might SSH into one of those servers, fix something specific to it, push the changes out to the other local servers so that they're all synced, and repeat for weeks and months on end.

And because each of those repos are equally "official", all branching and merging operations are equally easy on each one of the peer machines. Although it's conceptually possible that it could be just as easy on a VCS that doesn't work with full clones, I've never seen it.

Re:Why SQLite Does Not Use Git by puchatek on Sunday July 23, 2023 @02:54AM (#36833126)
Interesting usecase. The "git bad for everything else" commenter was probably unaware of it. That said, it's not very representative of what git is mostly used for and where there comparison with fossil is least favorable.
Re:Why SQLite Does Not Use Git by genocidicbunny on Sunday July 23, 2023 @03:41AM (#36833348)
It seems you're still largely talking about mostly text files. The parent you're replying to works in video games, where 99% of the data stored in VCS by volume (if it's even stored in VCS) is not text data. It is things like textures, audio files, processed geometry..etc. It is extremely easy to have one single texture take up more disk space than the entire source code for the game.

> I can clone a remote repo, then work independently for months.

If you're working with more than 0 other people in video games, good frakking luck doing this. If you're working on a large enough game, you're also going to need potentially multiple TB of storage just to have a full shallow copy of the repo (with just the latest copies.) I have worked at a studio where a full deep clone of the repo for just one game was well over 100TB. Let's see you load that up on your laptop.

Re:Why SQLite Does Not Use Git by maccard on Sunday July 23, 2023 @06:30AM (#36834076)
Even not in games, moving away for months at a time with no coordination is a recipe for disaster.
Re:Why SQLite Does Not Use Git by kstrauser on Sunday July 23, 2023 @12:04PM (#36836603)
The don’t use Git for it. Emacs is a crappy Photoshop replacement, but it’s great at it was actually built for. Git isn’t great for video game assets, but it’s great at what it was actually built for.

Use the right tool for the job. The parent poster is complaining that their employer picked the wrong tool for their job, then insisting that the tool sucks.

Re:Why SQLite Does Not Use Git by forrestthewoods on Monday July 24, 2023 @12:36AM (#36843152)
You’re missing the point.

Git is optimized for a specific use case. This prohibits other use cases. I think Git could be slightly tweaked to optimize for and enable different use cases. I think far more users would benefit from the new use cases than the old.

I want to use the right tool for the job. I wish Git were changed slightly so that it could be the right tool.

Git is not capable of handling video game assets. It could be. I wish it were. You may may be happy as is. I think you would actually be happier if my use case were supported. Because I think Git is over optimized for an ultra niche case that doesn’t matter to most users. And yes I realize most users are not game developers.

Git is great at what it was built for. Almost all current Git users do have the same requirements as the thing Git was built for. Therefore Git is a sub-optimal tool for almost all users. The world deserves an optimal tool. The hegemony of Git and GitHub makes it difficult for an optimal tool to be made and therefore all users suffer.

Re:Why SQLite Does Not Use Git by ylyn on Sunday July 23, 2023 @01:42AM (#36832825)
You can't really have branches, commits and merges _while offline_ without a distributed repository.

Let me add to that: history and blame too.

Re:Why SQLite Does Not Use Git by lelanthran on Sunday July 23, 2023 @03:56AM (#36833416)
> Or on a plane. It’s nice to have 100% of its functionality when you have 0% of your usual connectivity. Branches, commits, merges, all from the local file system? Yes, please.

You don't need the VCS to be a distributed VCS to have offline capability.

> There’s a reason we moved off centralized VCS en masse.

No, there's a reason we moved to git specifically. We didn't move to the competing DVCS, did we?

Re:Why SQLite Does Not Use Git by LordShredda on Saturday July 22, 2023 @10:06PM (#36831921)
Not an issue, if remote goes down you can always restore from backup
Re:Why SQLite Does Not Use Git by hprotagonist on Saturday July 22, 2023 @10:33PM (#36832061)
having been the guy who did that: i assure you, doing it is An Issue.
Re:Why SQLite Does Not Use Git by KerrAvon on Sunday July 23, 2023 @12:48AM (#36832623)
I was once responsible for doing this with a Perforce server. Only time in my career a VCS has lost data. This was decades ago now and the data loss might have been due to hardware; I cannot definitively blame Perforce, but man was it shitty to deal with at the time. We migrated to Subversion and never had another issue.
Re:Why SQLite Does Not Use Git by hprotagonist on Monday July 24, 2023 @07:23PM (#36855604)
watching inodes fail before my eyes was … not an experience i’d care to repeat
Re:Why SQLite Does Not Use Git by genocidicbunny on Sunday July 23, 2023 @03:32AM (#36833303)
I would love to see a DVCS that can effectively handle repos of the size I've seen. How well does DVCS work when your repo is about 10TB?
Re:Why SQLite Does Not Use Git by hprotagonist on Monday July 24, 2023 @11:34AM (#36849660)
https://github.com/microsoft/VFSForGit

better than it used to, with the caveat that git in particular is not and has never claimed to be good at versioning blobs.

Re:Why SQLite Does Not Use Git by layer8 on Sunday July 23, 2023 @04:21AM (#36833517)
Local history doesn’t imply D. The D basically means that clients and servers are equivalent. You could have a centralized VCS with client-server asymmetry and still have local history.