Here is my perspective, limited as it is. 1. You can not get by without learning Objective C! 2. Objective C really isn't that bad! As a minor upgrade to C it is fast to pick up, the bulk of your learning will go to the various APIs. This if you already know a little bit of C. 3. If you want to write apps right now Objective C is the best way to go. Now I know that many will object to that statement and I have to admit that MacRuby is getting better everyday but MacRuby is still far from complete. Well maybe not far but I think you should grasp what I mean. 4. IOS and MacRuby are currently mutually exclusive. This is actually the biggest bummer of any point I have listed so far. If you are interested in iOS devices there is no good reason to even bother with MacRuby. 5. Now things are not all negative here. For one all platforms need a well integrated scripting language. MacRuby certainly fills that role but it isn't Python. Now we don't want to argue the finer points of scripting languages but I find I use Python more than MacRuby because of prior experience and sometimes a better fit for the problem. So what I'm saying is that MacRuby is sorely needed as a way to build MacOS type apps. 6. MacRuby's status at Apple is unclear. This can be somewhat frustrating because I'd rather that Apple officially support MacRuby. Apple does seem to be extremely focused on the "C" dialects only. Maybe my impression here is wrong, but I'd rather see MacRuby shipped by Apple as part of their developer tools set officially supported. MacRuby should be as important to Apple as Visual BASIC is to MS.
In the end it is up to you. MacRuby is a very interesting project and is why I follow this forum. For the time being though I do not use MacRuby. The lack of iOS support is one big issue. The fact that you have to learn Objective C and the APIs anyways is another. I'm also pressed for time and know at least a little C++ so Objective C is the less painful approach. Also consider this, I made the decision to stay with the C languages a very long time ago. MacRuby is far closer to complete now so the Alpha/Beta nature is slowly going away. Sent from Dave's iPad! On Oct 15, 2011, at 8:12 PM, Bryan Harrison <br...@bryanharrison.com> wrote: > Older & Wisers: > > Having done enough web development, network design, and systems > administration for one lifetime, I've decided this winter is a fine time to > leave all that behind and become an applications developer. Wanting to make > consumer products and having no interest in Windows, most of the territory > ahead is obvious. > > But still, I'd appreciate some advice from those who're already there, > particularly with regard to MacRuby. > > Specifically, has development for OS X and iOS reached the point where it > would be reasonable to pursue Ruby before or even instead of Objective-C? > I've modest C background, am OOP-familiar, am not versed in Cocoa, and am > only marginally familiar with Ruby. Obviously I'd like to get up to speed as > soon as possible, but I'm not under any pressure and expecting this will be > the next 5-10 years of my life, would rather be good than quick. > > Objective-C is not without a certain homely charm, but Ruby is obviously the > more modern language. So… > > Does Xcode treat Ruby as family, or is it a stepchild toiling in the ashes? > Are there other tools I'll need? > > What's Apple's attitude toward Ruby applications? > > Can Ruby take advantage of the (finally!) modern memory management features > released with iOS 5? > > Will I end up have having learn Objective-C regardless? > > Basically, "If you were me, what would you do, and what order might you do it > in?" > > Thanks, > Bryan > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
