Nifty, though having used both languages I don't know why you would want to use Java instead of Objective-C. Plus it's not the language that matters most, it's the Cocoa libraries, which you'll still need to use anyway (I suppose that could be an argument <i>for</i> using whatever language you're comfortable with, but I feel Objective-C is particularly well suited for Cocoa)<p>It seems a little ridiculous to convert Java source code to Java bytecode to XML, then use XSLT to convert to Objective-C source code, but I guess if it works...<p>Also, there's a few inaccuracies:<p>a) Apple isn't just <i>planning</i> on adding garbage collection to Objective-C, Objective-C 2.0 <i>already</i> has it (though it's not available on iPhone, for whatever reason)<p>b) He says it's a downside that there's no strong compile time type checking, but really the warnings the compiler gives you that your class hierarchy doesn't implement a selector are pretty much equivalent to the Java compiler telling you it can't find a method. Just enable -Werror if you want to treat warnings as errors.