Comment by kennywinker

Well any way you slice it you're still going to have to interface with the Cocoa frameworks that make up the OS. Anything that masks the interface too much just causes friction. e.g. you can't look stuff up in the docs anymore.

MacRuby does a bit better job at first glance than this does, but you can't get past the way the framework you're using works.

In Objective-C:

    Person *person = [Person new];
    [person name];
    [person setName:name];
    [person setFirstName:first lastName:last];

and in MacRuby

    person = Person.new
    person.name
    person.setName(name) 
    person.setFirstName(first, lastName:last)

As far as I can tell in MobiRuby that'd look something like this:

    person = Person._alloc._init
    person._name
    person._setName _S(name)
    person._setFirstName _S(first), :lastName, _S(last)