I have kind of mixed opinions on that part. I also run OSX largely for those reasons, but it's been quite frustrating in some ways that Linux isn't. The good is

I have kind of mixed opinions on that part. I also run OSX largely for those reasons, but it's been quite frustrating in some ways that Linux isn't. The good is that many things do often "just work": wifi, multiple monitors, sleep, etc. And the power management is good. The bad is that if something doesn't work, it's much harder to debug, and the support is much worse. Everything feels very opaque and inscrutable in comparison to the Linux world. Example: I had a recurring issue on a MacBook Pro after upgrading from 10.6.x to 10.9.x where some process called 'systemstats' would balloon to taking 4gb of RAM or so, usually for about an hour. This was triggered by all sorts of things, from the daily Spotlight indexing, to clicking on the power display on the top/right menu bar (essentially anything that invoked systemstats would cause it to go haywire). Looking around the internet, some other people had the issue, and had all sorts of possible ways to fix it, with no solid confirmation from Apple of anything, and fixes that didn't work. So it was trial and error, things like manually deleting some BerkeleyDB files to see if that'd solve the problem, someone even suggesting resetting PRAM, whatever that means. Eventually I settled on writing a script that just did a 'killall systemstats' every 5 minutes. Huge hack, but fixed the symptoms. That way of debugging problems really sucks compared to what I was used to from previously running Debian. There, you either file a bug or find an existing bug, which serves as a central clearinghouse where people really try to determine the root cause of the problem and fix it. Apple doesn't really do anything like that, so you end up reading a bunch of disorganized threads on random mac forums, hoping someone has a diagnosis/fix.