When you try to install git it forces you to install Command Line Tools for XCode (whatever the f that is) which can take an unknown time to download, force you to accept a license and breaks, and force you to reinstall them at least once a year (or randomly the next time they break something)
Did you know that GCC take an unknown time to download, and forces you to accept a license?
I think it’s pretty common knowledge that Macs are sold as consumer machines that don’t include a full tool chain out of the box. Guess what - it’s free to download and sometimes it gets updates.
It’s hard to understand why you are making such a fuss about installing developer tools on a developer machine.
Sometimes I find I have to install gcc or clang or llvm on a Linux machine in order to install some other package. Why would I moan about this?
> Did you know that GCC [...] forces you to accept a license?
No it doesn't. The GPL is only relevant if you plan to distribute GCC, and you are never made to affirm your agreement when downloading, installing or using GCC. GCC never prompts you with any "click agree to continue" bullshit.
> Prompt or no prompt, if you use GPL software, you are forced to accept the GPL.
No prompt, no forced acceptance. You are simply wrong. The GPL permits all use, it has no restrictions on use. It restricts only distribution.
> This is no different from Apple’s license, which also allows you to use the software freely unless you want to redistribute it.
You are wrong. You didn't read Xcode's license. I did, it places substantial restrictions on how and where you can use Xcode, not just restrictions on distribution.
Limits on distribution are limits on use. If you don’t understand that, I suggest you Google for some discussions about why many people don’t use GPL’s software - it’s because the limits on distribution affect their usage.
Fair point about the XCode license being more restrictive than I said.
