Re:Xamarin makes me sad, here is my message to them
by eropple on Monday September 22, 2014 @02:01AM
(#8349457)
My experience with Ruboto has not been good. Gave it a try during a sojourn away from Xamarin (which I use for the game I'm making, but Ruboto was for something else) and its perf was really unfortunate on a Nexus 4, not much better on a Nexus 5. You'll end up writing anything nontrivial in Java anyway, making a lot of it moot.
Re:Xamarin makes me sad, here is my message to them
by srgpqt on Monday September 22, 2014 @07:34AM
(#8350113)
RubyMotion now has builtin (beta) support for Android.
http://blog.rubymotion.com/post/97668474211/announcing-the-p...
Re:Xamarin makes me sad, here is my message to them
by AlexeyBrin on Monday September 22, 2014 @11:30AM
(#8350946)
This seems like a viable approach in the future. I hope you are not suggesting that it is OK to send code compiled with a beta version to a client.
Re:Xamarin makes me sad, here is my message to them
by vinceguidry on Monday September 22, 2014 @01:04PM
(#8351386)
> I hope you are not suggesting that it is OK to send code compiled with a beta version to a client.
If the client's demanding a single-codebase solution for both Android and iOS and you are better at Ruby than you are with either Java or Objective C, then it might make sense to sell the client on using the beta.
Re:Xamarin makes me sad, here is my message to them
by AlexeyBrin on Monday September 22, 2014 @04:39PM
(#8352501)
I guess it depends on the client, if he is willing to take the risk that, for e.g., his app won't be compilable with the final version of RubyMotion. You can probably convince him it is a good idea if you specify in your contract that you will offer support in the future when RubyMotion for Android is stable.
I think RubyMotion could be a good idea, even today, for someone that knows and use Ruby for his own projects.
Have you considered Ruby? With Ruboto for Android and RubyMotion for iOS, I'd think you could get a pretty good single-codebase solution. I ask because as a Ruby dev who may one day branch out, I'd like to know what I'd be getting myself into, and it sounds like you might have gone down that road.