‹ BackHN Continuity

Thread

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

570 points · 536 comments · chmaynard

  1. thunderfork · · focus · HN ↗
    A lot of replies here seem to be asserting that this "isn't that hard" without addressing the thing that makes it most hard: submodule compatibility and the breadth of tooling
    1. pixl97 · · focus · HN ↗
      Submodules are a mistake.
      1. purpleidea · · focus · HN ↗
        > Submodules are a mistake.

        Someone started this FUD a long time ago and it has worked. Instead of using an elegant mechanism, project have built inelegant wrappers on top of git like go.mod which are actual mistakes.

        1. hnlmorg · · focus · HN ↗
          I’m not the author but I agree with their opinion.

          Compare the UX of go mod with git submodules. One is easy and the other is about as fun as having teeth extracted.

          git’s UX has never been its strong point. But submodules takes that pain to a whole new level.

        2. okanat · · focus · HN ↗
          It is the same people who say Git is unseasonably hard to learn. It isn't. Git and its command line is ugly and hard to remember. Understanding what those commands do at a commit and a branch level isn't really difficult. Even the internal object model is only moderately difficult.

          I say this as a person who strongly dislikes many many aspects of Unix and Linux due to bad design and terrible UX. Git has a better design than any Unix program you get.

          Submodules work okay. It is just Git LFS but for Git repos. Get over it.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.