Git 3.0's upcoming SHA-256 default will be a costly mistake
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Git 3.0's upcoming SHA-256 default will be a costly mistake
Unofficial Hacker News client; not affiliated with Y Combinator.
MBCook · · focus · HN ↗
So this is the right time to post that everything they’re doing is wrong? Did you engage in all the discussions about it and how best to handle it? Whether SHA-256 was the best solution?
I don’t see anywhere that it talks about alternate proposals or why they might have been better. Why the particular suggestions here were rejected.
This seems like a bunch of Monday morning quarterbacking.
nofunsir · · focus · HN ↗
MBCook · · focus · HN ↗
fragmede · · focus · HN ↗
nofunsir · · focus · HN ↗
fragmede · · focus · HN ↗
In what way has git's discussion of their move been hidden away in a metaphorical basement?
nofunsir · · focus · HN ↗
Mailing lists are basements in 2026
fragmede · · focus · HN ↗