Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

RubyMotion - Ruby for iOS

rubymotion.com

Post reply on HN
Print view View original

141–150 of 250 posts

Re: RubyMotion - Ruby for iOS

#141

Post by coffee »

chc wrote: post #127
coffee wrote: post #123

Earlier quoted context omitted.

> That's a bit like saying, "Remove the concept of putting on running shoes and warming up and only require that I run a marathon and I'm FAR quicker." It's not at all like saying that. Feel free to keep your words out of my mouth :) > ...is insignificant compared to the time it takes to learn Cocoa. I see you've changed from using the word "easy" to the word "learn." That's a step in the right direction :) Though, w…

I know you aren't comparing the time it takes to learn Cocoa vs. Objective-C. My point is that if you did make the comparison, you'd realize that if you have the time to learn Cocoa, you have the time to learn Objective-C, because the latter takes basically no time compared to the former. You get a time savings of like 0.05% by learning MacRuby instead of Objective-C.

No hostility :)

You're just on the defensive, so it feels like hostility. It's understandable...

> My point is that if you did make the comparison...

But I didn't.

I never compared the two.

My statement was one of a speed gain by simply using the languages/tools you're most familiar with, instead of learning new languages/tools.

It cuts out a lot of time, it's not a hard concept to understand ;)

Re: RubyMotion - Ruby for iOS

#143

Post by jgavris »

I don't understand all the hate for Objective-C, and at the same time love for Ruby. Objective-C is far easier to read, with named parameters and types everywhere. Ruby is often so minimal that you need to interpret the whole program yourself to understand what's going on...

Re: RubyMotion - Ruby for iOS

#144

Post by sthulbourn »

It's nice, I'm new to using ruby (I've been an iOS dev for a while now), I'd give it ago.

But I assume it uses storyboards in the same way as ObjC, set it in the target and in the Info.plist, and it figures it out... it'd be nice to see it working though.

Re: RubyMotion - Ruby for iOS

#145

Post by chc »

coffee wrote: post #141
chc wrote: post #127

Earlier quoted context omitted.

I know you aren't comparing the time it takes to learn Cocoa vs. Objective-C. My point is that if you did make the comparison, you'd realize that if you have the time to learn Cocoa, you have the time to learn Objective-C, because the latter takes basically no time compared to the former. You get a time savings of like 0.05% by learning MacRuby instead of Objective-C.

No hostility :) You're just on the defensive, so it feels like hostility. It's understandable... > My point is that if you did make the comparison... But I didn't. I never compared the two. My statement was one of a speed gain by simply using the languages/tools you're most familiar with, instead of learning new languages/tools. It cuts out a lot of time, it's not a hard concept to understand ;)

> No hostility :)

> You're just on the defensive, so it feels like hostility. It's understandable...

Really, no. I don't know if it's intentional or not, but you come across as very passive-aggressive and condescending. I don't even know what it is I'm supposed to be "on the defensive" about — the fact that learning Objective-C takes much less time than learning Cocoa? I feel pretty secure in that knowledge.

> But I didn't.

> I never compared the two.

Yes, that is my point — your opinion has no sense of scale, because you haven't compared the two. You're talking about saving pennies on the price of a sports car. I just don't think it's a particularly pressing concern. If you're that worried about pennies, you're probably not in a position to buy that car.

But, you know, whatever works for you.

Re: RubyMotion - Ruby for iOS

#146

Post by mattgreenrocks »

hlidotbe wrote: post #28
mattgreenrocks wrote: post #22

Earlier quoted context omitted.

In the Ars article, I noticed the author mentions you can't use XCode's layout tools. In practice, how big a problem is that?

I tried a bit, technically it works but currently you have to compile your xib to nib manually using ibtool. That may have changed tough because I dropped the xib as I didn't really needed it.

How does that work? Layout the view, convert the XIB to NIB, and load it at runtime?

Re: RubyMotion - Ruby for iOS

#147

Post by cheald »

ScotterC wrote: post #62
cheald wrote: post #12

Earlier quoted context omitted.

There are already exclusive libraries for MRI/JRuby, so adding a third platform doesn't seem like it would break the world. Tools like Bundler do a great job of keeping things moving smoothly.

Didn't realize bundler kept track of what ruby you were using.

Yeah, check the "platforms" directive.

Re: RubyMotion - Ruby for iOS

#148

Post by SeoxyS »

bherms wrote: post #54

Just a note, not sure if this is intentional, but the audio on the video is in stereo, but with no right channel. edit: also, please stop the heavy breathing into the mic. Driving me crazy!! :)

I could not watch the video (on headphones) because it is physically painful to do so. That's a HUGE problem.

Re: RubyMotion - Ruby for iOS

#150

Post by chc »

freditup wrote: post #138

My thoughts: "Hey! This looks pretty neat. Oh it's $150 on sale, forget this. Oh it's only for macs, glad I never bought this piece of garbage." That being said, it could be great, I have no idea.

The iOS SDK itself is only for Macs. It seems like a reasonable requirement for something that depends on the SDK to run on the same platform.
Post reply on HN