11–20 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.
I refuse to hammer this nail with a hammer. I will use a screwdriver. I will go through great difficulties if need be, so that I can keep on using a screwdriver.
If you are saying the former, I agree entirely. If you are claiming the secondary, than I have to ask what do you think the purpose of a language like Lua is? Why do programmers like using Lua in combination with their c/c++ projects?
Oddly, 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…
Disclaimer: I've not built anything extensive with Rubymotion/IB, but I have built a proof of concept. I don't know if it's really feasible on a large project.
Also, Obj-C and Ruby share many common concepts, using Cocoa from RubyMotion usually requires just a bit of syntax swapping, "vanilla" RubyMotion is not much of an abstraction.
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
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
I don't hate objective c / XCode nearly enough to pursue a solution like this even though I like and appreciate ruby. In my opinion the only way this would be the future is if apple started providing support for it.
The REPL is kind of cool, but then he doesn't remember how to set the label text. There's no statement completion or help for him in the console, so he gives up. He's stuck. He'll spend way more time reading docs and figuring out Cocoa method sigs than just learning the XCode toolset and discovering methods in the editor.
That said, overall it's a good talk and I applaud his efforts at explaining the tool - I just think it's not clear RubyMotion is a net positive in terms of productivity.
I don't hate objective c / XCode nearly enough to pursue a solution like this even though I like and appreciate ruby. In my opinion the only way this would be the future is if apple started providing support for it.
The only issue is that I would prefer to work with another editor. XCode just doesn't have some of the editor features I am used to with other IDEs.
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.