Why I'm Not Using RubyMotion in Production
joshsymonds.com
Why I'm Not Using RubyMotion in Production
1–10 of 75 posts
Re: Why I'm Not Using RubyMotion in Production
#2I have been waiting for a post like this for a long time. There seems to be a distinct lack of "I use rubymotion and here are my thoughts" type posts that provide concrete details.
Really appreciate the article and I am interested to see where this leads for RubyMotion.
Re: Why I'm Not Using RubyMotion in Production
#3I just bought a RubyMotion license and I really enjoyed creating my first iPhone App but I don't think I would have started if I knew about this issue.
I really hope that they get around to fixing this problem, it does make me a bit concerned that they are pushing big new features while such a serious issue seems to exists.
Re: Why I'm Not Using RubyMotion in Production
#4While RM-3 itself is only 4 months old, the bug's been around and discussed since RubyMotion first came out (e.g. http://blog.blazingcloud.net/2012/07/16/rubymotion-block-sco...).
They used a bug tracker that wasn't publicly viewable until they migrated everything to YouTrack earlier this year (I reported it last August).
Re: Why I'm Not Using RubyMotion in Production
#5While RM-3 itself is only 4 months old, the bug's been around and discussed since RubyMotion first came out (e.g. http://blog.blazingcloud.net/2012/07/16/rubymotion-block-sco... ). They used a bug tracker that wasn't publicly viewable until they migrated everything to YouTrack earlier this year (I reported it last August).
Laurent himself replied to that blog post saying the bug was resolved in RM v1.20. What's the difference between RM-3 and what that post describes? They read very similar to me.
Re: Why I'm Not Using RubyMotion in Production
#6We must be able to expect that critical flaws in our toolchains will be fixed promptly
At some point, Borland disabused me of the notion that serious toolchain providers fixed their critical flaws promptly... or at all.
Re: Why I'm Not Using RubyMotion in Production
#7I just bought a RubyMotion license and I really enjoyed creating my first iPhone App but I don't think I would have started if I knew about this issue. I really hope that they get around to fixing this problem, it does make me a bit concerned that they are pushing big new features while such a serious issue seems to exists.
This is exactly how I'm feeling now. I've been prototyping and loving it, but I almost don't even want to try releasing an application if the support burden is going to be that high...
Now it's like, well, why not just use Objective-C? I sort of just wish I had my $200 back.
Re: Why I'm Not Using RubyMotion in Production
#8I just bought a RubyMotion license and I really enjoyed creating my first iPhone App but I don't think I would have started if I knew about this issue. I really hope that they get around to fixing this problem, it does make me a bit concerned that they are pushing big new features while such a serious issue seems to exists.
You can get a refund within 30 days.
Re: Why I'm Not Using RubyMotion in Production
#9Am I the only one who thinks that ARC in a language like Ruby is probably impossible? Even with Objective C they had to add 4 new variable qualifiers, and put that burden on the programmer to use them properly.
Re: Why I'm Not Using RubyMotion in Production
#10Apologies for the basic question, but why would this 'analog' (is that another system? An abstraction?) have this issue if it is using ARC? Isn't ARC just a flag in XCode's compiler? If RubyMotion turns it on, wouldn't XCode make all the necessary arrangements? Again, I simply want to understand; I'm not trying to make a point.