[groby_b]

Apples open source devtools are old as dinosaurs, so that might be a common case.

But more importantly, it's the question whose laptop it is. I continue to think that the tools I build go to /usr/bin, because that's the way I like it. Apple is telling me I'm liking it wrong.

As for filing a bug with Apple - good one. Every single Apple dev considers radr:// a black hole, and the chance of getting a fix from Apple because of bugs filed (vs. Apple wants to fix it anyways) is slim to none.

Overall, Macs are more and more machines that want to prevent shooting yourself in the foot, at the price of less flexibility and access. This is a good choice for some, it's not a good choice for me. (And many other people who like hacking their machines)

[Hamuko]

>Apples open source devtools are old as dinosaurs, so that might be a common case.

Yeah, but there's a certain expectation that the tool that you have installed in /usr/bin is a certain version. There's a reason why tools like Homebrew generally do not overwrite built-in tools.

If you just replaced /usr/bin/python with Python 3, you'd probably break all kinds of things.

[groby_b]

The point is, it is my machine to break. Apple is more and more deciding that I don't get to do that. It's a choice that benefits a large class of customers, but it's detrimental to people like me.

macOS used to be "Unix, but with a great GUI". It is turning into "iOS, but with a few command line tools".