[ubernostrum]

I switched about four years ago because my employer issued me a MacBook Pro; for the previous six years I'd been using Linux full-time as my desktop OS. It took... well, hardly any time at all to get used to it.

Admittedly, I still spend most of my time in Terminal and a lot of what I knew transferred immediately (minus the quirks of going from GNU tools to BSD), but even in the GUI parts of the OS there wasn't anything that really surprised me. And once I'd learned the standard keyboard shortcuts I was rather pleased with how completely consistent even third-party applications are about implementing them (a situation which didn't, at the time, exist with most of the GNOME apps I'd been using).

[jdietrich]

I had the same experience, switching from Debian to a Mac. The only moments of confusion I had on switching were things that were too intuitive. Coming from a Linux background and remembering dependency hell, I couldn't quite get my head around the idea that to install an application you just drag and drop it into the application folder. As soon as I stopped trying to second-guess the system and just did what I thought would be the obvious thing, everything became obvious!

Of course the terminal just feels like home, OSX is a proper *nix and everything works as you'd expect it to. The big difference is that everything else works as you'd expect it too as well. It seems like some sort of dream that I used to spend a whole week setting up a new computer, fiddling with drivers and dependency problems and xorg.conf nonsense.

[pyre]

Don't espouse the platform too much. Maybe it's stable now, but there were plenty of issues early on. I got a Mac around the release of MacOS 10.2.

If you mounted an NFS or Samba share the filesystem driver would 'beachball' the entire operating system if the server ever became unresponsive. There were numerous times where the smbfs driver caused kernel panics too. The only improvement to this offered in 10.3 was a dialog that would popup asking if you wanted to disconnect the share whenever it deemed that the server was unresponsive. Though the 'timeout' that it was using to display this dialog was too conservative. Sometimes it would popup just to disappear right away when it finally get a server response. [Note: these shares were mounted over a LAN, not spanning across the internet or something] The issue hurt me the most when I left a share mounted at home when I closed my PowerBook, only to wakeup the PowerBook at school/work and have OSX require a forced restart because the server was no longer there.

{edit} I know that all platforms have issues, I just get annoyed when people act like they don't.