I'm wondering what performance penalties, if any, would your app incur for using one or the other as opposed to objective-c?
With a game move search algorithm I did recently, I found that my Obj-C was 30x-40x faster than my Ruby version. YMMV, of course, depending on the nature of the code. For that particular computationally intensive situation, Obj-C was necessary.
For many ordinary apps, I have found Ruby to be plenty fast. Python, in my informal tests, is a bit faster than Ruby -- anywhere from 10% to 40%.
Ruby, however, is simply a joy to use. I'd use it all the time if I could. Once YARV (the on-the-fly compiler in development) is added to the Ruby distribution, Ruby should double, or more, in speed.
by Jim — Dec 13
With a game move search algorithm I did recently, I found that my Obj-C was 30x-40x faster than my Ruby version. YMMV, of course, depending on the nature of the code. For that particular computationally intensive situation, Obj-C was necessary.
For many ordinary apps, I have found Ruby to be plenty fast. Python, in my informal tests, is a bit faster than Ruby -- anywhere from 10% to 40%.
Ruby, however, is simply a joy to use. I'd use it all the time if I could. Once YARV (the on-the-fly compiler in development) is added to the Ruby distribution, Ruby should double, or more, in speed.