1. 5

  2. 15

    What is the opening paragraph even trying to say?

    You can see this if you look at stackoverflow questions about submodules. What’s wrong with submodules? Well, compared to what exactly?

    Huh? Who’s asking this? What questions?

    But I’d like to suggest that this pattern will probably apply to Go, Rust and whatever else.

    Why are you suggesting this?

    This whole post feels like a rant about something so specific, so esoteric, that it just doesn’t apply to most people. I have a hard time even tracking what the problem they’re describing is. People expect something different about git? Why do you give a shit?

    1. 5

      Yeah, I had a very hard time trying to figure out what this was even about. Apparently the OP doesn’t like submodules. No idea why. ¯_(ツ)_/¯

      “Use your language features instead” … I guess that’s nice when your language has a package manager (unlike, say, C/C++), which is more featureful than Git, and your repo only uses a single language, and the ecosystem your repo is part of only uses a single language.

      This seems sort of like a JavaScript equivalent of White Privilege, somehow. Tossing out advice without even realizing that it only makes sense because you’re sitting atop this huge ecosystem you breathe like air, not realizing not everyone works the same way you do. (Not that I’m equating this to racism, just making an analogy.)

    2. 4

      “Using git’s well-documented features” (such as submodules or hooks) is hardly “tricking git”. You want to use CI instead of hooks, how do you think your CI system knows when you push? Oh, it’s hooks.

      1. 3

        I think I’ve read too much tech lately, but I have been struck by how much people talk about git. It’s literally meant to do one thing well: track changes to text files. And we still discuss it incessantly. I think that’s part of the point the author was trying to make: foisting all this stuff on something that labels itself a dumb content tracker. We put the expectation that it should somehow convey our engineering process onto it and then act surprised that it isn’t the best carrier of that information.