Why RubyMotion Is Better Than Objective-C
joshsymonds.com
Why RubyMotion Is Better Than Objective-C
1–10 of 70 posts
Re: Why RubyMotion Is Better Than Objective-C
#2I'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
#3Re: Why RubyMotion Is Better Than Objective-C
#4It's a higher level language, which allows you to get more work done faster. Case closed.
Re: Why RubyMotion Is Better Than Objective-C
#5Re: Why RubyMotion Is Better Than Objective-C
#6Not 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.
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
#7Re: Why RubyMotion Is Better Than Objective-C
#8Re: Why RubyMotion Is Better Than Objective-C
#9I 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.
Re: Why RubyMotion Is Better Than Objective-C
#10I am not sure if the RubyMotion approach is different than Titanium -- does anyone know whether it is faster and why?