That's impressive. I suppose they had a more flexible architecture to make that change so fast.

Is there any writeup on why it was easy for them and not for git?

toymin 9 hours ago | parent | next [-]

My guess is that it's less about the architecture and more about the blast radius and the number of users

gandreani 9 hours ago | parent | prev [-]

Hmm probably nothing architecture wise. It's probably just the fact that fossil is developed by way fewer devs.

From the skim I read of this article it seems both projects arrived at the same solution: support both but make SHA-256 the default.

	▲	kccqzy an hour ago \| parent [-]
		No it’s different. Git supports both but you cannot mix them in a repo. Fossil allows mixing them in a single repo. This is clearly stated in the link.