PyObjC isn't, but ships in Mac OS X. That's rather officially supported.
> * it binds to Cocoa (and if you're lucky it's even up to date and doesn't have that many bugs)
Not true. MacRuby is a prime example of a language that taps directly into the Objective-C runtime, eliminating the need for a bridge. And PyObjC is a great example of a mature bridge – it's been around and robust since the NeXT era.
MacRuby is an Apple project.
PyObjC isn't, but ships in Mac OS X. That's rather officially supported.
> * it binds to Cocoa (and if you're lucky it's even up to date and doesn't have that many bugs)
Not true. MacRuby is a prime example of a language that taps directly into the Objective-C runtime, eliminating the need for a bridge. And PyObjC is a great example of a mature bridge – it's been around and robust since the NeXT era.
> * you can't use it on iOS
http://mobileorchard.com/announcing-iphone-wax-native-uikit-...
> * you can't get a job doing X instead of Obj-C because almost everyone just uses Obj-C, the Apple supported language
You can't get jobs programming Ruby, Python, C#, Lua or any other language?