Live data from Hacker News

Why RubyMotion Is Better Than Objective-C

joshsymonds.com

1–10 of 70 posts

Re: Why RubyMotion Is Better Than Objective-C

#2
The lack of IB support makes the otherwise "Ruby that Looks Too Much Like Objective C" a bit of a net loss. You lose IB, and the ability to easily integrate the approaches all the thousands of examples and questions do.

I'm very interested to see where this ends up however. I'd love to do iPhone programming (with IB support) in python or ruby. Just not with this tool, just yet.

Re: Why RubyMotion Is Better Than Objective-C

#6
post #3

Not that it's an invalid position , but when Apple-centric developers proclaim 'ObjC > C++' in such a matter-of-fact way, I always wonder how much that is based on actual real-world experience.

Well see part of the problem is that it takes more experience to know your way around C++; it's just bigger than Objective-C, even if you only talk about the "commonly used" parts. If you know C and are reasonably familiar with OO, you can easily learn all of the important differences between C and Objective-C in a week or so. And since it's a true superset, everything you know from C carries over. C++ is just more complicated to learn the ropes of.

So I guess what I'm saying is that a lot of people criticizing C++ probably don't have much experience with it, but that's kind of the point.

Re: Why RubyMotion Is Better Than Objective-C

#8
I would have killed for this about 2 years ago, but now that I learned Objective C, I'm comfortable enough with its quirks that I can just use it to get stuff done.. Having to learn the nuances of RubyMotion in order to do stuff I already know how to do, is probably very very low on my priority list.

Re: Why RubyMotion Is Better Than Objective-C

#9
post #4

I don't understand why anyone should have to justify this. It's like saying "Why C# Is Better Than C." It's a higher level language, which allows you to get more work done faster. Case closed.

Not case closed. Given that you lose a lot of useful tools (Interface Builder, Storyboards and such) and that Objective-C can be pretty quick to code with Xcode I would contend that given expertise in both a complex application would take less time to code in Xcode/Objective C.

Re: Why RubyMotion Is Better Than Objective-C

#10
As someone who has developed and released iOs apps in Titanium before (write JS / coffee, compile to native app), I am curious about RubyMotion's performance. One of Titanium's weaknesses is that it is extremely inefficient in certain views (e.g. tableViewsRows) to the point where if you are loading/sorting any appreciable amount of data you can only display a few labels within the view without the app grinding to a halt -- on average iPhones.

I am not sure if the RubyMotion approach is different than Titanium -- does anyone know whether it is faster and why?

Post reply on HN