Git 3.0's upcoming SHA-256 default will be a costly mistake
Scott Chacon argues that the upcoming transition to SHA-256 as the default hashing algorithm in Git 3.0 is a mistake. He contends that the change will cause significant global disruption for minimal practical benefit.
Why it matters
Git is the foundational tool for global software development; changes to its core architecture have massive implications for infrastructure and developer workflows.
Butler's Log RSS Downloads Docs Community Source code Join GitButler Downloads Docs Community Source code Today by Scott Chacon
I've been sitting on this for a few years, mostly because there are smarter people who have been concentrating on this and I don't love being a back seat driver. However, I think that the Git 3.0 release is about to cost everyone a lot of time and angst for little benefit, and virtually nobody knows what's coming.
So grab some popcorn and let me tell you a tale of how one of the new upcoming Git 3.0 breaking changes is about to be a huge, costly, global train wreck of a change for almost no practical value.
I'll keep this short as many of you probably know this at a basic level.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in