Live data from Hacker News

RubyMotion 3.0 Sneak Peek: Android Support

blog.rubymotion.com

31–40 of 80 posts

Re: RubyMotion 3.0 Sneak Peek: Android Support

#31

Maybe it's petty but I've lost confidence in Ruby Motion since I've had a pull request open against it for whole year because they don't support enterprise deployment out of box. The fix is pretty damn simple too https://github.com/HipByte/RubyMotion/pull/64/files You'd think enterprise would be a prime use case here. Sucks to have to keep your own fork up to date. Moral of the story, if you have a Github repo please…

I'm just smiling at the juxtaposition. It's amusing what in most circumstances would be a fact of life becomes a major sticking point. Apple doesn't take pull requests. I'm sure Google accepts patches, sometimes, but the process doesn't strike me as quite on the PR-level of ease.

Is the alternative PhoneGap, and the hypothesis that they're more responsible with taking ownership of your pet features? Just curious.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#33
post #4

"RubyMotion for Android features a completely new Ruby runtime specifically designed and implemented for Android development." That is huge, very excited to check this out! I would love being able to write ruby instead of java (whereas objc doesn't bother me that much).

> I would love being able to write ruby instead of java You can do that with InfraRuby ( http://infraruby.com/ ) if you don't mind writing type annotations.

Thanks for the downvotes! In case it's not obvious, this is a free download (follow the "Installation" link). A major update will be released next week!

InfraRuby compiles Ruby with type annotations to ordinary Java classfiles.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#34
post #3

I am elated. Rubymotion is awesome. It has the ease of PhoneGap with the speed of native Obj-C.

I just downloaded it and am impressed so far. Looks like it'll be an extra bonus since I won't have to also learn Ruboto to write Android apps with Ruby.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#35

Maybe it's petty but I've lost confidence in Ruby Motion since I've had a pull request open against it for whole year because they don't support enterprise deployment out of box. The fix is pretty damn simple too https://github.com/HipByte/RubyMotion/pull/64/files You'd think enterprise would be a prime use case here. Sucks to have to keep your own fork up to date. Moral of the story, if you have a Github repo please…

Might I suggest posting a comment on that pull just to bump it?

Re: RubyMotion 3.0 Sneak Peek: Android Support

#36
post #6

"The object model of RubyMotion for Android is based on Java. Ruby classes, objects, methods and exceptions are Java classes, objects, methods, and exceptions, and vice-versa. No bridge is involved." But then later it says "The runtime uses the Java Native Interface (JNI) in order to integrate with Java". And then later it says, "RubyMotion Android apps are fully compiled into optimized machine code, exactly like the…

That jumped out to me too. There is a significant performance hit when you make JNI calls. Last I looked not all of Android's API are easily exposed to native code. Constantly context switching from native to managed can be beastly. I'd be curious on how often and when it is doing these JNI calls, what is native and what is java.

Sorry when you say native versus Java what do you mean? As far as I was concerned all native apps are java?

Re: RubyMotion 3.0 Sneak Peek: Android Support

#38

I was just looking at the rubymotion licences [0]. does anyone know if you will get future releases with the licence? do you only get them for one year? [0] http://sites.fastspring.com/hipbyte/product/rubymotion

> does anyone know if you will get future releases with the licence?

Yes.

> do you only get them for one year?

Yes, though license renewal costs $100, not $200.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#39

Earlier quoted context omitted.

That jumped out to me too. There is a significant performance hit when you make JNI calls. Last I looked not all of Android's API are easily exposed to native code. Constantly context switching from native to managed can be beastly. I'd be curious on how often and when it is doing these JNI calls, what is native and what is java.

Sorry when you say native versus Java what do you mean? As far as I was concerned all native apps are java?

Native machine code, he means, rather than "native to Android" Java bytecode.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#40
post #31

Maybe it's petty but I've lost confidence in Ruby Motion since I've had a pull request open against it for whole year because they don't support enterprise deployment out of box. The fix is pretty damn simple too https://github.com/HipByte/RubyMotion/pull/64/files You'd think enterprise would be a prime use case here. Sucks to have to keep your own fork up to date. Moral of the story, if you have a Github repo please…

I'm just smiling at the juxtaposition. It's amusing what in most circumstances would be a fact of life becomes a major sticking point. Apple doesn't take pull requests. I'm sure Google accepts patches, sometimes, but the process doesn't strike me as quite on the PR-level of ease. Is the alternative PhoneGap, and the hypothesis that they're more responsible with taking ownership of your pet features? Just curious.

PhoneGap works well so does Xcode or anything that doesn't aim to replace the typical processes.

It's just such a stupid thing with their rake command, it checks to see if your device is provisioned to save you an unsavory error message. Since I have an Apple Enterprise account I am not subject to the 100 device limit and having to provision the device's UDID; so they're checking a non-existent array in the provisioning profile.

Less a pet feature, more an edge case with "rake device" that they missed. It's like they're completely oblivious to an entire class of provisioning profiles in their tooling.

Which doesn't speak well to the maturity of the tool, have they seriously never dealt with an enterprise customer or for that matter an app that had more than 100 devices beta testing it? Almost every iOS development firm I know uses the enterprise provisioning profiles since it's a more simple process than having to juggle UDIDs.

Post reply on HN