Live data from Hacker News

RubyMotion 3.0 Sneak Peek: Android Support

blog.rubymotion.com

51–60 of 80 posts

Re: RubyMotion 3.0 Sneak Peek: Android Support

#52
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.

Google is pretty famous for letting Android contributions sit in a review queue forever to die. They effectively don't accept.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#53
I was impressed that even with all this translation and Java compatibility going on, the sample code still shows some situations where the nice clean, concise nature of Ruby is still up and running. E.g.:

> @paths.each { |path, paint| canvas.drawPath(path, paint) } if @paths

From: https://github.com/HipByte/RubyMotionSamples/blob/master/and...

And: @activity.handler.post -> { @activity.updateTimer }

From: https://github.com/HipByte/RubyMotionSamples/blob/master/and...

These things take a lot of lines in Java for Android where we don't have lambdas and function references yet and often have to define anonymous classes just to pass a method in to a handle to be run later.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#54
post #52
post #31

Earlier quoted context omitted.

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.

Google is pretty famous for letting Android contributions sit in a review queue forever to die. They effectively don't accept.

I've accepted and merged a fair number of patches. It's a matter of getting the right reviewers and working with the people involved in each of the areas to come up with a reasonable patch if it's anything other than a small bugfix.

That being said, it does depend on the area (some are totally in AOSP, some move fast internally and only get AOSP drops occasionally), and bug fixes are a far easier than features to get merged.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#55
post #48

Earlier quoted context omitted.

I disagree. Somebody that doesn't want to spend $200 on a product with a complete-satisfaction guarantee probably won't be a very good long-term customer. The RubyMotion guys are filtering out the low-end of the market, which from a business perspective, is a good move.

Um.. no. Sorry. I haven't done that for desktop software since the early 2000s. You're asking for a lot of damn money on nothing but faith. Besides, every crappy product advertised on TV ever offers a "money back guarantee", and some cursory googling should show that those often aren't worth the electrons used to transmit the image to the screen. This is the internet age, and we're talking about software. You get pai…

I can attest, as a RubyMotion early adopter, the product and especially the customer service make the $200 entry point and $100 service renewal well worth it.

If excellent customer reviews and a real money-back guarantee don't convince you, then I'm not sure a free trial will either.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#56
post #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.

Actually, the license is good forever. The $100 is for updates and support.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#57

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?

https://developer.android.com/tools/sdk/ndk/index.html

Re: RubyMotion 3.0 Sneak Peek: Android Support

#58
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).

You can't 'check it out' though unless you pay £123.47 for the privilege.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#59
post #31

Earlier quoted context omitted.

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.

I submitted a pull request to fix a dead link in the angularJS docs: I was told to fill a 20-text field form for the request to get processed. I was just trying to help, guys.

I assume you meant the Google CLA. It's only 8 fields and you only have to sign it once.

https://developers.google.com/open-source/cla/individual

Re: RubyMotion 3.0 Sneak Peek: Android Support

#60

Earlier quoted context omitted.

I submitted a pull request to fix a dead link in the angularJS docs: I was told to fill a 20-text field form for the request to get processed. I was just trying to help, guys.

I assume you meant the Google CLA. It's only 8 fields and you only have to sign it once. https://developers.google.com/open-source/cla/individual

Yes but it's still enough irritation to put people off. It feels like 'not getting it'.

There must be a better way to keep the lawyers on their leashes?

Post reply on HN