‹ 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. MBCook · · focus · HN ↗
        I don’t understand what this is supposed to mean.
        1. fragmede · · focus · HN ↗
          nofunsir is a stoichastic parrot, matching to a bit in Hitchhikers Guide to the Galaxy, wherin the protagonist should have known to protest a plan to demolish his home where plans where clearly documented in a hard to find place that they could not have known about. It is not a good pattern match, because git has been discussing this in public on documented mailing lists for years.
          1. nofunsir · · focus · HN ↗
            No I'm not. Real thumbs here. If anything this paragraph sounds like LLM slop
            1. fragmede · · focus · HN ↗
              Run it through pangram if you want, I wrote it with my human brain. What I did not do, however, was parrot an inapplicable quote.

              In what way has git's discussion of their move been hidden away in a metaphorical basement?

              1. pcthrowaway · · focus · HN ↗
                That comment was short enough that you'd really have to be naive to think a tool could reasonably detect if it was authored by an LLM.

                Additionally, as someone who read Hitchiker's guide to the Galaxy ~3 decades ago, I managed to suspect it was a reference to it, even if the reference wasn't the most applicable

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.