I really feel like you believe I'm arguing that you shouldn't use Ruby or RubyMotion. I'm not! Ruby has been my go-to language for half a decade now. Heck, I even follow both the MacRuby mailing list and Twitter list. To reiterate, this is the entirety of my argument:
> "I don't want to go to the trouble of learning Objective-C" is a weak reason to use RubyMotion, because you'll have to do 99.95% of the same work anyway.
The fact that Ruby can express things very concisely has nothing to do with whether or not learning Objective-C adds an appreciable amount to time to the process of learning Cocoa. That's why I was ignoring it. If you simply like Ruby on its own merits, that's a good reason to use it.
> The fact that Ruby can express things very concisely has nothing to do with whether or not learning Objective-C adds an appreciable amount to time to the process of learning Cocoa.
Here's the disconnect. That was never my point.
Please re-read my initial comment. You responded to that comment, hence you're responding to my initial point, which has nothing to do with your argument.
Do you get it?
The problem is your just not able to express your point, clearly, in relation to the context of this topic. Maybe face-to-face, verbally, you'd do a brilliant job of it. But in the written form, well... Not so good.
A little humility on your part would go a long way. Just saying ;)
> "I don't want to go to the trouble of learning Objective-C" is a weak reason to use RubyMotion, because you'll have to do 99.95% of the same work anyway.
The fact that Ruby can express things very concisely has nothing to do with whether or not learning Objective-C adds an appreciable amount to time to the process of learning Cocoa. That's why I was ignoring it. If you simply like Ruby on its own merits, that's a good reason to use it.