> It was originally more of a historical artifact of all of the tooling being deeply steeped in Apple's own tech stack. I would say that it is tied to an insti

> It was originally more of a historical artifact of all of the tooling being deeply steeped in Apple's own tech stack. I would say that it is tied to an institutional memory of what can go wrong when your platform depends on third party development tools. Back in the classic Mac OS days, most developers used a compiler toolchain (Codewarrior) and application framework (PowerPlant) from a company called Metroworks. They were bought by Motorola and those products were discontinued leaving developers in a bind. After that, Apple decided that they needed to offer their own first party development tools.