Thread

Git 3.0's upcoming SHA-256 default will be a costly mistake

570 points · 536 comments · chmaynard

MBCook · 1790876427 · focus · HN ↗
So they’ve been talking about this for many years, planning, and finally announce when they’re going to switch the default.
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.
1. nofunsir · 1790876779 · focus · HN ↗
  The plans have been on display in a cellar. Beware of the leopard.
  1. MBCook · 1790877296 · focus · HN ↗
    I don’t understand what this is supposed to mean.
    NikolaNovak · 1790877478 · focus · HN ↗
    It's a hitchhiker guide to the galaxy reference, where sure, something is technically available but not clearly published and there are hoops even for those who know what they're looking for.
    (No clue if it's applicable here, I'm not aware of this case, but I believe that's the reference if it helps :)
    Edit : exact quote, as Arthur's house is about to be demolished for a highway bypass:
    "But the plans were on display…”
    “On display? I eventually had to go down to the cellar to find them.”
    “That’s the display department.”
    “With a flashlight.”
    “Ah, well, the lights had probably gone.”
    “So had the stairs.”
    “But look, you found the notice, didn’t you?”
    “Yes,” said Arthur, “yes I did. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard.
    Dylan16807 · 1790878125 · focus · HN ↗
    It's not at all applicable.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.