Rubymotion – Myth, Magic, or The Future?
bostonrb.org
Rubymotion – Myth, Magic, or The Future?
1–10 of 24 posts
Re: Rubymotion – Myth, Magic, or The Future?
#2Re: Rubymotion – Myth, Magic, or The Future?
#3Re: Rubymotion – Myth, Magic, or The Future?
#4Oddly, I didn't run away from Objective-C and Xcode screaming. But I have run screaming away from Ruby on Rails a number of times. I do acknowledge that this is likely a personal shortcoming though.
Re: Rubymotion – Myth, Magic, or The Future?
#5The insight alone from seeing a new corner of the programming world is worth biting the bullet and learning something new.
Re: Rubymotion – Myth, Magic, or The Future?
#6Oddly, I didn't run away from Objective-C and Xcode screaming. But I have run screaming away from Ruby on Rails a number of times. I do acknowledge that this is likely a personal shortcoming though.
But Cocoa is the thing you have to learn no matter what. To be honest, all things considered I would rather put up with Objective-C than lose Interface Builder and the niceties of XCode.
And I say that even though I have used and love PyQt. Cocoa is so deeply married with Objective-C and XCode, I can't really see the point of using RubyMotion.
Re: Rubymotion – Myth, Magic, or The Future?
#7Re: Rubymotion – Myth, Magic, or The Future?
#8Re: Rubymotion – Myth, Magic, or The Future?
#9Oddly, I didn't run away from Objective-C and Xcode screaming. But I have run screaming away from Ruby on Rails a number of times. I do acknowledge that this is likely a personal shortcoming though.
Ruby is cool. REPLs are cool. Objective-C is slightly weird. Interface builder is kind of nice. XCode is weird, but has some fairly great features for Objective-C/Cocoa. But Cocoa is the thing you have to learn no matter what. To be honest, all things considered I would rather put up with Objective-C than lose Interface Builder and the niceties of XCode. And I say that even though I have used and love PyQt. Cocoa is…