News for hackers. Stuff that matters.
Re:RubyMotion Success Story: Cabify by hans_olo on Thursday August 30, 2012 @11:02AM (#4454951)
Hmm, I have used Cabify and it's a horribly slow application. Now I know why.
Re:RubyMotion Success Story: Cabify by cicloid on Thursday August 30, 2012 @11:08AM (#4454976)
- "We hope to launch a new completely redesigned app in the next few weeks, as opposed to months!"

It seems the app for common users is not the RubyMotion app.

Re:RubyMotion Success Story: Cabify by rebo on Thursday August 30, 2012 @11:23AM (#4455039)
They are not using Rubymotion for their customer app yet.
Re:RubyMotion Success Story: Cabify by jcromartie on Thursday August 30, 2012 @11:26AM (#4455053)
No, you don't. Of all the things I have against RubyMotion, performance is not one of them.
Re:RubyMotion Success Story: Cabify by javierhonduco on Thursday August 30, 2012 @11:04AM (#4454960)
As far as I'm concerned, Rubymotion shoudn't decrease the performance of an app...
Re:RubyMotion Success Story: Cabify by firlefans on Thursday August 30, 2012 @11:26AM (#4455057)
Yup Rubymotion isn't interpreted, it's compiled file by file to LLVM bytecode, this negatively effects development speed but it means it runs (roughly) as fast as pure obj-c (or so they claim on the rubymotion site). We're using it at the moment to develop an app, it's great at keeping code DRY, debuggability on device kinda sucks atm though.
Re:RubyMotion Success Story: Cabify by thibaut_barrere on Thursday August 30, 2012 @11:07AM (#4454971)
Given how RubyMotion works (not an interpreter unlike regular Ruby), if the app is slow (I didn't test!) then it's very likely not related to RubyMotion.
Re:RubyMotion Success Story: Cabify by batista on Thursday August 30, 2012 @12:25PM (#4455365)
I call BS.

Your other comment in the same thread does not mention you using Cabify at all -- it's a general slant against the company for using "unproven technology".

And your account was created one hour ago, just to deliver these two negative comments here.