Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Monkaaay

macrumors 6502
Original poster
Jun 19, 2006
258
0
Richmond, VA
Has there been any official word on the future of non-Objective-C languages on the Mac platform? I feel like Apple has really shifted away from Java support and I'm wondering how they'll handle Python, Ruby, and others.
 

HiRez

macrumors 603
Jan 6, 2004
6,265
2,630
Western US
Well I don't know how recently you mean, but with Leopard, Ruby and Python both have officially supported Cocoa bridges. So there's more support than ever for them. Java support is definitely out though, and I don't see it ever coming back.

To open up the benefits of the Cocoa frameworks to a wider developer audience, Leopard embraces two other highly dynamic languages for use in building Cocoa applications: Ruby and Python. These two languages are an excellent fit for integrating with the Cocoa frameworks, and they both have high quality bridges to Objective-C. These bridges allow you to mix and match Objective-C, Ruby, and Python, allowing you to choose the best tool for the job at hand while using high level Cocoa features such as Key-Value Coding (KVC) and Key-Value Observing (KVO).
 

Monkaaay

macrumors 6502
Original poster
Jun 19, 2006
258
0
Richmond, VA
Right, and that's my concern with Python and Ruby. Apple seems to "pull the plug" quickly on these things without a lot of notice. Java support and Carbon come to mind. I'd hate to work on something only to have support for it pulled from under my feet without warning.
 

HiRez

macrumors 603
Jan 6, 2004
6,265
2,630
Western US
Right, and that's my concern with Python and Ruby. Apple seems to "pull the plug" quickly on these things without a lot of notice. Java support and Carbon come to mind. I'd hate to work on something only to have support for it pulled from under my feet without warning.
Yeah, I know what you mean. Python and Ruby are currently on a "more supported" trend, but you're right, that does not guarantee future support at all, especially from the mercurial Apple. Java was on the same track for a while too and became abandoned quickly. Objective-C (and C) and Cocoa are the only truly safe bets, those are not going anywhere anytime soon, as long as OS X is around, and it looks like it will be for along time. I love Python, but for that very reason I'll be sticking with Objective-C for my Mac development. Another reason is that AFAIK, the Python and Ruby bridges are not supported for iPhone development (I'm not even sure the runtimes are available on the iPhone).
 
That's always a risk but the good news is that both Python and Ruby come from open source backgrounds - these efforts existed before Apple took official interest and when the fall from favour they will very likely still remain under development. From a business perspective, these also require less work for Apple and fill a gap (a RAD environment) for them.

Apple haven't really met expectations in terms of keeping OS X a top level Java development platform but I guess they do have to make sacrifices to pursue other areas. Java has a strong corporate and embedded presence, where Apple is not really interested or has their own plans. Java support requires developer time but Apple will only really be playing catch up while they continue to build their own VM and cannot really lead; all the best tools are cross-platform anyway. Maybe with the open-sourcing of Java (and that one bloke managed to get that running on OS X on his own) will convince Apple to join the effort. On the other hand ... work had to get me a new MPB so I could work on Java 6 compatibility :)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.