21–24 of 24 posts
I think one of the most interesting points about the presentation is the BubbleWrap libraries. The greatest pain I've felt with iOS development are some of the terrible APIs. The amount of ceremony needed to Parse JSON from a web based API request or to access the camera is almost absurd.
Well, here are two short snippets on how to do that. It is incredibly easy. (Sorry, I couldn't find a better paste it host.) http://paste.org/53022
This fear of learning a new tool, language or API boggles my mind. The insight alone from seeing a new corner of the programming world is worth biting the bullet and learning something new.
I think your comment is great, and equally applies to experienced Objective-C developers who could miss something interesting here :)
Earlier quoted context omitted.
I think your comment is great, and equally applies to experienced Objective-C developers who could miss something interesting here :)
Good point, although, an experienced Objective-C developer can already write iOS apps - learning Ruby in the context of backend development would probably be more beneficial. It'd be like asking Michael Jordan to play basketball left-handed instead of playing baseball.
Similarly, I'm making the quick bet that we will see a interesting number of experienced Obj-C developers move to RubyMotion! (well, as someone who is on the RubyMotion list, I can tell some have already started).
The challenge isn't Xcode or Objective-C but rather the Cocoa Touch API. At the end of the day you still need to contend with the API, no matter which framework you use.