What's so hard about objective-c? If you stay mostly-in-objc, it's not much different than ruby/python -- it's just method calls with named parameters. If you use any framework in ruby, you're probably already doing something similar since many method calls take in a hash where you pass in options.
Everything else after learning the syntax is just learning the api.
I think because kids nowadays never learned C/C++ like us old timers. Manual memory management trips them up. Obj-C's "weird" object oriented syntax becomes a non-issue in 2 hrs of coding, so it has to be the manual memory management and API design that are the issue.
UIKit and Cocoa are, admittedly, pretty unorthodox compared to pretty much a lot of UI frameworks out there. That and Interface Builder being a separate app were the biggest obstacles for me learning iOS programming.
Comments
What's so hard about objective-c? If you stay mostly-in-objc, it's not much different than ruby/python -- it's just method calls with named parameters. If you use any framework in ruby, you're probably already doing something similar since many method calls take in a hash where you pass in options.
Everything else after learning the syntax is just learning the api.
I think because kids nowadays never learned C/C++ like us old timers. Manual memory management trips them up. Obj-C's "weird" object oriented syntax becomes a non-issue in 2 hrs of coding, so it has to be the manual memory management and API design that are the issue.
UIKit and Cocoa are, admittedly, pretty unorthodox compared to pretty much a lot of UI frameworks out there. That and Interface Builder being a separate app were the biggest obstacles for me learning iOS programming.