How I ended up with Mac

iPhoto IS one. As I distinctly explained in my previous post, iPhoto comes installed on every every single Mac that Apple sells with the sole exception of the server configuration of the Mac Pro. Go to the Apple web page and click on any Mac and look at the "Built-in Apps" section, you will see iPhoto displayed right alongside "system" apps like Mac App Store, Mail, and Messages. iLife is just a marketing name. iTunes used to be part of iLife too. Now they're just apps, apps that 99.9% of people that purchase a Mac will find on their computers pre-installed when they open them. That was half my point: that iPhoto today is just about as much a part of a default installation of Mac OS X as any.

>Are you some naive end user OR an HN commenter that CAN tell the different between OS X and iPhoto, and doesn't complain about the latter on a thread about the first?

Now that we've gotten the fact that iPhoto will almost certainly be on my machine when I open it, it should be clear to you that it doesn't matter which of these I am. For better or worse, iPhoto is a part of the Mac experience. Drawing an imaginary line around a subset of applications and calling them "OS" or "not OS" does not take away from the fact that a bad iPhoto experience will understandably contribute to a bad Mac experience. As such, both by technical and laymen's understandings of OS, the critique is valid.

Edit: My mistake, iPhoto is included in the server one as well. So it turns out iPhoto comes installed on every single Mac.

If you want, of course, you can turn on locate, but it seems strange to have two local indexing things.

I've had no trouble installing Ruby, Python, Javascript, Mysql, Postgresql, GCC, Memcached on Mac OS X, mostly binary installers are available, or you can just use homebrew for stuff like memcached if not, I use rvm for Ruby as it's easier and ties in with server setups but you can install from source. So be aware that if you have run into problems it is not a universal failing of Mac OS X and was specific to you/your setup. I haven't seen many glitches with the above stack, and answers are usually googlable if you do run into something (for example after installing memcached I googled how to set up the plist homebrew provides to run it on startup). Can't say I've noticed much difference with upgrading/installing packages on linux, but then I tend to manage servers rather than desktops there.

I agree the package manager situation is more sane on Linux though if you're using open source code; it's one of the things Linux gets right (when it works), as opposed to commercial operating systems. That doesn't mean it's impossible or even difficult to use an open-source stack on Mac OS X though, quite the opposite.

He tried to poison Linux using Mono and that turned out to be an utter fiasco.

So he failed in destroying Linux and he's pissed that he failed. As a result he's now trying to cast some more bad light on Linux: this time Linux isn't an OS whose purpose would be to run CLR app but an inferior desktop/laptop app which shouldn't be used because OS X would be superior.

I'm a very long time Linux user (since the Slackware) days and honestly I've got zero love for that person (and, no, I'm not a Gnome user).