Live data from Hacker News

RubyMotion 3.0 Sneak Peek: Android Support

blog.rubymotion.com

61–70 of 80 posts

Re: RubyMotion 3.0 Sneak Peek: Android Support

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

Well: http://www.webkit.org/coding/contributing.html

Not pull requests, because not Git, but they do take contributions on some stuff.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#62
Hey, when it comes to mobile, I develop them in pure Objective-c for iOS, and pure Java for Android. I use tools provided by both compagnies. So yeah, I do the jobs twice, but I think it's ok.

Anyone have feedbacks coming from what I do to something like RubyMotion or Xamarin? These solutions sound very interesting, but I've yet to try them. I think I'm too attached to my Objective-c and workflow.

Also, is there peoples who originally used RubyMotion or Xamarin and went to use OC and Java?

Re: RubyMotion 3.0 Sneak Peek: Android Support

#63
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…

You've not experienced much of the high end market then. SAP / Oracle / many other enterprise apps cost thousands to tens / hundreds of thousands of dollars to license.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#64
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 have to say I have trouble taking comments like this seriously. $200 is "a lot of damn money"? Are you kidding? This is a professional tool for software developers. You do know you'll need a $100/yr ADC membership to even run your software on an iOS device, right?

Many developers have no problem whatsoever spending $200 on a tool like rubymotion, in fact I think it's a bargain. A money back guarantee is a bonus, and no-one has any reasonable doubt as to its legitimacy. I agree completely with the GP that this makes good business sense.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#65
post #9

I just wish they'd release an LOC limited trial version. I'd love to give it a spin, but I'm not about to fork out that much money just to try it...

I agree, and the 30 day trial isn't enough. It would be side projects, so I may get to hack on it for a day and maybe a night or two. I can write Obj-C, and Java, they just aren't as intuitive or enjoyable to me. And lets face it, $200 is just too much to spend when RubyMotion may not exist for version 4, and then I have an entire application that needs to be ported into Obj-C and Java... And a promise of open sourci…

> $200 is just too much to spend when RubyMotion may not exist for version 4

Do you see the contradiction here? I am happy, delighted even, to pay $200 (and then $100/yr) precisely because I know it is going to keep the company afloat for version 4, and 5, and 6. If anything I worry they are charging too little.

You want good things to exist, someone has to pay for them! Why is this so hard to understand?

Re: RubyMotion 3.0 Sneak Peek: Android Support

#66

Earlier quoted context omitted.

It could be a bad sign, or it could speak to priorities, and your priorities are not their priorities it seems. Personally, I accept all pull requests that are solid, written to my standards, fix or extend a feature that is a priority, are accompanied with unit tests, and do not impact or impinge on another feature or future feature. I do not however accept all pull requests. Part of this is that if there is no deman…

True, but if your business is alternative toolchains to Apple's own; and it's shown to me that you don't support something I know a great deal of iOS developers use then I lose a bit of faith in your marketing message that "lot's of important apps use us... and don't mind what all the naysayers say about our garbage collector, give us $200/year and give it a shot yourself". It's one thing that my pull hasn't been acc…

whose

Re: RubyMotion 3.0 Sneak Peek: Android Support

#67
post #9

I just wish they'd release an LOC limited trial version. I'd love to give it a spin, but I'm not about to fork out that much money just to try it...

Likewise. $200 is a lot of money to throw down on something sight unseen, money back guarantees or otherwise.

I bought it a year ago, used it heavily for a few days, decided that it was not what I needed, and they refunded my money.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#68
post #2

This is great news, it will boost the adoption of Ruby and RubyMotion in the huge Android market. Finally I have a reason to give RubyMotion a try. I'm curious how much productivity gain can one achieve with a language like Ruby once it is compiled (which will ensure the speed of the resulting application).

I think the gains are huge, but it depends on your preferred workflow. I know some traditional Xcode developers who kick and scream at the idea of loosing their IDE, whereas I prefer to live in the terminal.

Workflow is one thing, but then writing Ruby code is so fluid. Notice that there's not a lot of preamble (imports and such) that you need to take care of in the Ruby code, I think that's great. But, again, language and workflow are very personal, and I think every tends to "think they're right" ;-)

Re: RubyMotion 3.0 Sneak Peek: Android Support

#69

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…

Hi James, it's mostly my fault that your PR hasn't been merged. We tend to focus a lot on the compiler, and less on the Rake commands, but I'll try and get these PRs taken care of soon.

Re: RubyMotion 3.0 Sneak Peek: Android Support

#70

Hey, when it comes to mobile, I develop them in pure Objective-c for iOS, and pure Java for Android. I use tools provided by both compagnies. So yeah, I do the jobs twice, but I think it's ok. Anyone have feedbacks coming from what I do to something like RubyMotion or Xamarin? These solutions sound very interesting, but I've yet to try them. I think I'm too attached to my Objective-c and workflow. Also, is there peop…

If you already have a comfortable work flow, I would not encourage you to migrate just for the sake of it, but having the option to write a native app in Ruby is very compelling to a lot of people who might otherwise not be interested in writing a native mobile app.

RubyMotion supports xib files, storyboards, xcdatamodel files, and Android XML files (and localization files, etc), so if you ARE interested in switching, you don't have to stop using those if you're already used to them.

Post reply on HN