On a new macOS machine, you are basically tricked into installing git along with Xcode [1]. If you do so, you have to download an 8GB package, even if you only want git (which is my case and I can’t be the only one).<p>To make it even worse: on every system update git becomes unavailable, You have to accept your Xcode license to start using it again.<p>Is it me or it’s a terrible design? That’s super inconvenient, takes so much extra resource, and it's not even a one-time operation. And again, I couldn’t care less about Xcode, I just want my git.<p>What are the benefits of having within Xcode? I feel that if there are benefits, end-users aren’t the beneficiaries but Apple devs, which would be sad.<p>[1] https://forums.developer.apple.com/forums/thread/672087?answerId=659036022#659036022
><i>On a new macOS machine, you are basically tricked into installing git along with Xcode [1]. If you do so, you have to download an 8GB package, even if you only want git (which is my case and I can’t be the only one).</i><p>So, just install Brew, or MacPorts, or Nix, and use them to install just git, or just download a git binary directly. You can also download the smaller "Command Line Tools" package that includes git and clang.<p>The user is not really tricked: the XCode installer is neither meant, nor advertised as the way to get git when you just want git. Xcode installs various libs, tools, and, among them, git, for its own purposes. So, sure, if you want to use XCode you'll also get an installation of git, but the reverse is in no way necessary.