You're not really fair. Yes, it's true that osx has 3rd-party-package-manager. But it's also true that they can be very complicated, or simply broken. The easy'ness of a good linux-distribution is just not possibly with osx. The days where you need to hack yourself something togehter, just to get some basic applications, are gone...at least on linux.
You're not really fair. Yes, it's true that osx has 3rd-party-package-manager. But it's also true that they can be very complicated, or simply broken.
MacPorts is like FreeBSD ports and Fink is like apt-get. Brew is also dead-easy. While they're not perfect, there are some far more complicated systems in some Linux distros.
The easy'ness of a good linux-distribution is just not possibly with osx.
It is perfectly possible, as in nothing in OS X prevents it. It's just not happening/ed, because, well, not enough OS X users contribute to it, compared to the Debian/Ubuntu community.
Still, it's not that bad. I work with Ruby, Python, Node, C plus various web technologies, and use lots of unix stuff. I seldom have problems installing them with brew.
Also consider the alternative: I can install apps through the App Store or through a DMG image, that no Linux can run today (because they are native Cocoa apps). Stuff like Photoshop and Office, and Premiere, and Aperture, etc. The ease of installing industry standard proprietary apps lots of people need and a large number can't do without, is just not available in Linux.
As someone who administers a lot of Macs and a few LInux machines, package management on Macs is simply indefensibly bad. There is no getting around it. Apple chose not to provide this as a service to their users.
I use a Mac laptop and would never have written this post. But I don't have to pretend that the package installation setup on OSX is remotely acceptable. It is horrible. Stuff breaks or won't install all the time. On mainstream Linux distros, stuff generally Just Works.
Apple's users are not people that dive into the command line. Apple's users are people that open the App Store and have their "package management" solution.
Well, if Apple's users aren't the sort to dive into a command line, then most developers aren't Apple users.
Also, have you seen any modern, user friendly Linux distros (e.g. Ubunutu)? You never have to dive into the command line there and yet it has nice package management that just works.
Well, if Apple's users aren't the sort to dive into a command line, then most developers aren't Apple users.
Well if you have been to any developer's conference, you'd have deduced that most developers are Apple laptop users.
It's just that they don't bitch about any package that breaks.
Some of us also use a virtual machine like Fusion for an isolated environment if we want to do development with a Linux userland, we don't pile one on top of OS X and its' BSD core, and don't expect a volunteer effort like brew with 2000+ packages all sub 20K people use to work perfectly.
(The guy in the other comments said he manages multiple Macs (a sysadmin guy) and had troubles with installing the same packages to all, etc. Presumably also different OS versions. That's a slightly different problem.)
The doubtlessly depends on the developer conference in question; I bet an iOS conference and a .NET conference both have different distributions of mac users.
Looking at the recent StackOverflow survey[1] (I think it's fairly representative of developers in general), we see that about 20% of the respondents used Macs, another 20% used Linux and the rest Windows, so mac users emphatically do not represent "most" developers.
But my real point--which I realize was poorly worded--was not that no developers use macs but rather that the ones who do are not "Apple's users" in the sense calloc used.
It's been a long, long time command line tools are not required to use package management. Synaptic is a very easy interface to add new software and Ubuntu's Software Center, while a bit rough around the edges, is a very App Store like experience.
Besides that, package management also offer an easy way to keep your system updated. On a Mac, App Store excepted, there is no central way to keep your system up-to-date - Software Update will update Apple's software (often by downloading huge packages) and you are on your own to update whatever is left. Red Hat and Debian mastered this in the early 2000's.
As someone who uses both Linux(most familiar with Fedora and Ubuntu) and OS X regularly I have to say I completely disagree with you.
My Linux systems are always a headache. Last week I pulled a recommended patch from the system updater and it broke Xorg. I had to remove it by hand and reinstall it.
I don't buy that at all. If a serious distro pushed an update that broke X, we'd have all heard about it. Which distro? What package was it that broke? Are you sure you weren't mucking about with non-distro stuff like the NVidia driver installer?
The last time my X broke was a couple years back. Ubuntu pushed a defective update. Before that, the last time something like that happened was when I was using Debian Sid.
Breaking X is something you expect with Sid. And if you are running it, you re supposed to be able to fix it and submit a patch.
If you are breaking X, you are doing something wrong.
I think it probably depends on the distro, I've had quite a few systems break on Arch because I didn't read update warnings on the Arch Linux website after they had pushed a bad update.
Tangentially that is why I moved to xubuntu from Arch, though I'm sure Arch is a bit nicer with regards to headaches now.
Fedora likes to break frequently though I don't know if packages as big as X are likely to fall through the cracks.
Both Arch and, to a lesser extent, Fedora are aimed at more advanced users who want faster updates and newer technology over stability.
I think this is a great compromise, but it does mean you may have some issues with updates. That said, I have not had any issues on Fedora that weren't my doing.
I've been using Fedora for about a year. Earlier, I used OS X for about the same amount of time and I did have problems that weren't entirely my fault, largely with Java and Eclipse. Since all I was doing during that time was simple Java development for school, there just wasn't anything else that could have gone wrong.
