I have a Mac.  Nothing fancy, just a small MacBook.  I don't think it was a reaction to leaving Microsoft.  In fact, I dual-boot it with Windows Vista.  I need Vista because I am a Windows developer, after all.  Having said that, I have grown to like the Mac.  These days I'm doing most of my admin in the Mac partition, although I do use Microsoft Office:mac 2008.

Curiosity got the better of me, and I decided to try my hand at development on the Mac.  I should say that I was a C and C++ developer earlier in my career, which makes it easier for me to adapt to Objective-C Cocoa development than would be the case if I had only done .NET development.

There's a lot I could say by way of comparison between Mac Cocoa dev and .NET development for Windows.  Maybe I will say more about it at some point.  For now, let me just say that .NET developers have a much easier time of things than our Mac brethren.

Some of my time at Microsoft was spent in a marketing group, and one of the facts of life there is that, among all Microsoft's customers, developers are some of the harshest critics of the company.  All I can say is, some of those developers should try building apps for the Mac.  I think they might have a bit more love for Microsoft afterwards :-)

For a long time Microsoft has courted developers.  I think their focus on maintaining a productive development platform has helped their success in no small part.  Apple on the other hand seems to do almost nothing for developers.  Their online documentation is extremely dry compared with MSDN, and their development tools are idiosyncratic, to say the least.

So, .NET developers, consider those worse off than yourself :-)  And if Apple ever gets its act together and produces an online developer marketing channel* to rival MSDN then Microsoft will really have something to worry about.

I haven't given up on Mac development.  It's harder, but that's not necessarily bad.  It's always useful to have more strings to your bow.

*yes, MSDN is a marketing channel.  You knew that, didn't you?