Hacker News Reader

Parent Full thread

6thbit

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?

View on HN

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

no it's about the architecture and design: fossil enables coexistence of both hashes in one repo

https://fossil-scm.org/home/doc/trunk/www/hundredandone.md

27. Fossil allows both legacy SHA1 hashes and newer SHA3-256 hashes in the same repository.

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.

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.

They should let you mix it in a repo then.

They do apparently. There's information about it in the comment thread on this story on lobste.rs

SHA3-256 != SHA-256

Oops! I admit I don't have much knowledge on hashing algos. I thought it was a shorthand

Reply on news.ycombinator.com