RubyMotion - Ruby for iOS

Post by 286c8cb04bda » Thu, May 03, 2012, 7:35 PM UTC

jballanc wrote: post #82

286c8cb04bda wrote: post #66

Earlier quoted context omitted.

What language features does Ruby have that Objective-C lacks? It's a bit more succinct, perhaps, but when you're calling out to Cocoa all the time, that succinctness is going to get thrown out the window.

Ruby has "yield" which, while possible to replicate in Obj-C, it's not nearly as nice. Also, Ruby can yield arguments, and the block being yielded to is free to ignore those arguments. That's the sort of flexibility that can make Ruby so much more enjoyable to work with in high-level code.

Post by [deleted] » Thu, May 03, 2012, 7:38 PM UTC

286c8cb04bda wrote: post #66

andybak wrote: post #25

Earlier quoted context omitted.

Or they've been spoiled by certain language features and it seems unbearable to go backwards.

What language features does Ruby have that Objective-C lacks? It's a bit more succinct, perhaps, but when you're calling out to Cocoa all the time, that succinctness is going to get thrown out the window.

Post by tlear » Thu, May 03, 2012, 7:47 PM UTC

Post by deeds » Thu, May 03, 2012, 7:53 PM UTC

phillmv wrote: post #53

sjtgraham wrote: post #32

I don't see the point of this. Objective-C is not hard to learn, and with ARC, blocks, the new literals for NSArray and NSDictionary, etc, Objective-C has actually become pleasant to write IMO. The example RubyMotion code also doesn't look very nice either. The problem with Rubyists (being one for the past 6 years I feel qualified to say this) is in general they want to use Ruby for everything. It's not always the be…

> Rubyists in general want to use Ruby for everything. Well… why not? This is a relatively objective statement; the problem with ruby tends to be the crappy interpreter we're forced to suffer through - not the language itself. The Ruby language, in my biased opinion, as far as OO-functional languages go is pure awesome. My initial reaction was: "A Ruby to Obj-C ABI compiler? Fuck no, what is wrong with you." Upon lea…

Post by conradev » Thu, May 03, 2012, 7:59 PM UTC

randomdata wrote: post #85

jballanc wrote: post #76

Earlier quoted context omitted.

I think you'll find the difference between working with Cocoa APIs in Obj-C vs Ruby is that it's much easier in Ruby to turn what you've learned into a simple, boiled-down, easier to digest set of helper methods/objects/modules. For example, in using the RubyMotion beta, after I understood the UIView animation flow, I created a helper method using "yield" to do the actual animation. If I were working in Obj-C, it wou…

Isn't that really the difference between something like: def animate UIView.begin_animation yield UIView.commit_animation end animate do # Do something end and: void animate(void (^block)(void)) { [UIView beginAnimation]; block(); [UIView commitAnimation]; } animate(^ { // Do something }); Which to my eye are pretty much exactly the same. In fact, UIView already provides a similar method built into the API. Anyway, I…

    [UIView animateWithDuration:0.5f animations:^{
        // Do something
    }];