4 ms·
I don't think you have much of an alternative if you want to make good software for iOS. As for programming for OS X, cocoa has bindings for ruby, so that shoul
by hmottestad 15y ago
I don't think you have much of an alternative if you want to make good software for iOS. As for programming for OS X, cocoa has bindings for ruby, so that shouldn't be a problem. https://secure.wikimedia.org/wikipedia/en/wiki/RubyCocoa https://secure.wikimedia.org/wikipedia/en/wiki/RubyCocoa
- jmonegro 15y agoIndeed. Even though I know I'll eventually transition to Objective-C, I was wondering if learning MacRuby first would tender down the learning curve by easing me into how Apple development works by leveraging my existing knowledge. What do you think?
- hmottestad 15y agoI would just go for objective-c. MacRuby is in version 0.1 and might be more of a headache to figure out and circumvent bugs and holes then just learning objective-c. It's not a very difficult language and easy enough if you have tried C or Java before. You'll also need to handle memory (allocation and deallocation), but you could try to rely on GC, but not for iOS. Lynda.com has a video tutorial on objective-c and also tutorials on iOS programming.
- lrz 15y agoMacRuby was version 0.1 about 3 years ago. A lot happened since, and we expect the next release to be our 1.0 RC. For Cocoa development, it's very stable, we haven't received any critical bug report since at least 3 releases.
- hmottestad 15y agoAh. I read 0.10 and thought 0.1. It's a logical mistake to make since 0.1 is a number and is the same as 0.10, I know a lot of other people count releases the same way, but skipping 0.10 might be a bit helpful, or keeping to a strict 0-9 policy. I saw Linus got tired of the 2.6.39 counting and just skipped ahead to 3.0.
- ddagradi 15y agoRubyCocoa is severely out-of-date. MacRuby is its replacement.