+1 I have a lot of time for Objective-C and Cocoa for desktop and mobile development. I'd go so far as to say it's a huge factor in the success of the Mac and

+1 I have a lot of time for Objective-C and Cocoa for desktop and mobile development. I'd go so far as to say it's a huge factor in the success of the Mac and iPhone platforms. It's pretty unique in supporting AOT, compiled-to-native executables while offering dynamic language and runtime features. However the reasons it works so well for those purposes (low memory footprint, fast application startup time) don't seem very relevant for server development - and the downsides (#1 being the ability of coding mistakes to corrupt memory and/or abort the process) become huge liabilities for a server. So my guess is that this framework is going to come out on the wrong side of any cost/benefit analysis.