lrz promises fix by next version
https://groups.google.com/d/msg/rubymotion/x6-9c__IHH0/J7jYd...
Why I'm Not Using RubyMotion in Production
71–75 of 75 posts
Re: Why I'm Not Using RubyMotion in Production
#72I 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.
If you're curious to hear more perspectives on using RubyMotion in production, you might check out Clay Allsopp's blog posts (e.g. http://clayallsopp.com/posts/rubymotion-year-one/ ). His startup has been using RubyMotion for a while and he's written tutorial and a book for it as well.
Very interesting! Thanks a ton for the tip.
Re: Why I'm Not Using RubyMotion in Production
#73Earlier quoted context omitted.
The fact that there is a workaround is irrelevant for two reasons. First, said workaround would completely change the entire structure of your ruby code. Basically, kill blocks. This is inferior to Objective-C itself structure-wise. Second, and most importantly, this bug is not something that jumps out at you. It only causes crashes in some small % of runs. So, the result is your apps look fine, you are writing idiom…
I think "irrelevant" is a poor choice of words here. It is VERY relevant that there is a workaround. Additionally, it's kind of unfair to point at 1 bug (that has a workaround) and judge an entire system on it. https://yourlogicalfallacyis.com/composition-division https://yourlogicalfallacyis.com/no-true-scotsman https://yourlogicalfallacyis.com/the-texas-sharpshooter
You basically just said "No, you" and then posted some links to logical fallacies. Care to address my argument more directly? The key problem here is that while this bug that may have a workaround (and that workaround is questionable to even work in all cases), it's that the bug does not manifest itself in a development environment, and occurs when you write code naturally. So, you are likely to introduce the bug, but you don't get to know you have crash issues all over your app until you ship it to a lot of users. This, combined with the App Store review delay process, results in a situation where this platform is not tenable for professional software developers to use.
edit: Laurent (RubyMotion lead) has chimed in and raised the priority of this issue, this is great news
Re: Why I'm Not Using RubyMotion in Production
#74Earlier quoted context omitted.
Did you know you can have Vim keybindings in Xcode?
As it happens, ViEmu has just launched their product on XCode as well. From the couple of days in use, I'm quite pleased with it in comparison with Vicious that I used before that. http://www.viemu.com/download-xcode.html
Thanks for the tip, I'll check it out!
Re: Why I'm Not Using RubyMotion in Production
#75Earlier quoted context omitted.
The XVim plugin? That's hardly a complete implementation.
xvim is super alpha... the visual studio guys just released a vim plugin for xcode too... I haven't used the xcode one yet but if it's as good as the visual studio one it should be very good. (I have contributed to xvim and I have purchased the visual studio plugin)
I might have to look into this visual studio plugin, thanks.