‹ BackHN Continuity

Thread

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

570 points · 536 comments · chmaynard

  1. MBCook · · 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 · · focus · HN ↗
      The plans have been on display in a cellar. Beware of the leopard.
      1. bawolff · · focus · HN ↗
        This isn't really applicable. The plans have been talked about for a while very publicly.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.