3 ms·
All your points go off at a tangent to the original article. 1). Author doesn't claim that most Mac owners are developers. He attributes "a large part" of Ap
by rm445 16y ago
All your points go off at a tangent to the original article.
1). Author doesn't claim that most Mac owners are developers. He attributes "a large part" of Apple's success to recommendations that began with developer mindshare.
2). It's not a burden to use the dev tools if you plan to use the dev tools, but it's a burden to install something on the scale of Xcode if some other tool you want to run just depends on the basic gcc toolchain.
3). For the author's points, you're not comparing Xcode installation to installing visual studio, you're comparing it to '[package manager] install gcc'.
4). Article author's preferred solution is not to stop charging, but to have a separate gcc package.
It boils down to the author thinking Macs would be more developer-friendly if more essential build tools (as opposed to developer tools, if you will) were bundled with the OS. It's an interesting point.
- scott_s 16y agoBut they are bundled with the OS. They're just not installed by default. Personally, I have a Mac, and I installed XCode for gcc. I've never used XCode itself. I did not consider it a burden; I did it once, over two years ago, as a part of setting up my MacBook. I have not thought about it since. Optimizing something that I do once everytime I get a new computer is of marginal value.