Hacker News Reader

That's surprising. Doesn't it seem like one big file would increase the odds of a sync conflict?

There is an extensively tested sync protocol, the whole file does not get synced each time.

https://fossil-scm.org/home/doc/trunk/www/sync.wiki

I think the original comment was talking about a generic sync utility, not about Fossil's or Git's own protocols:

> so it’s extremely to just back it up or keep the repo in cloud storage

A single big file seems like it would cause more issues for a generic sync utility. Though I guess I can imagine sync algorithms that work better with one style vs the other.

for simgle users (hobby projects) that's not a concern. For teams, you'd go through a hosted server anyway.

Sure, but the original post said that it was a concern for Git but not for Fossil. I was wondering why that is.

Reply on news.ycombinator.com