Why RubyMotion Is Better Than Objective-C

Re:Why RubyMotion Is Better Than Objective-C by trebor on Friday May 04, 2012 @12:43PM (#3929217)

Could you explain:

    - RubyMotion is Ruby
    That's great. Ruby is a great, easy to use and powerful language. I love Ruby. However given all the other things you sacrifice to get Ruby it's really not worth it.

What do you sacrifice to get to use Ruby? I've avoided learning to program iOS because I really dislike Obj-C. If Ruby were good enough for 60% of the apps on the App Store I'd join in a heartbeat.

[ Parent | on HN ]

Re:Why RubyMotion Is Better Than Objective-C by poutine on Friday May 04, 2012 @12:57PM (#3929289)

- No Interface builder. Really a big loss given the power of Storyboards/segues, layout of objects, complex flows.

- No syntax/error checking as you type

- No static analyzer

- No code completion (perhaps you could find a 3rd party module to do this eventually)

- No refactoring support (very important in larger projects)

- Probably longer compilations (in Xcode/ObjC the compiler will know which files are modified by looking at the included headers and only recompile what is needed, in Ruby I would expect it's gotta do them all but could be wrong).

[ Parent | on HN ]