Why RubyMotion Is Better Than Objective-C

Post by cageface » Fri, May 04, 2012, 4:14 PM UTC

poutine wrote: post #19

- Objective-C is Hard to Use It has a much steeper learning curve than Ruby for sure, but once you're proficient it's no harder to use. Indeed there's benefits to both languages. - Xcode is Unstable It's gone through periods of instability. But in the current version you may encounter the odd crash (perhaps once a week in full time use for me). Really not an issue given it's a cutting edge tool that's rapidly evolvin…

Post by mistercow » Fri, May 04, 2012, 4:14 PM UTC

Derbasti wrote: post #17

mistercow wrote: post #6

Earlier quoted context omitted.

Well see part of the problem is that it takes more experience to know your way around C++; it's just bigger than Objective-C, even if you only talk about the "commonly used" parts. If you know C and are reasonably familiar with OO, you can easily learn all of the important differences between C and Objective-C in a week or so. And since it's a true superset, everything you know from C carries over. C++ is just more c…

Exactly. C++ is simply way more complicated than Obj-C. Also, the Obj-C object system is pretty high level and dynamic (message passing, late binding, dynamic dispatch). This makes it somewhat slower at method calling, but at the same time a lot easier to work with. The downside of being slow is usually mitigated by simply being able to drop back to plain old C if need be. Of course, C++ can emulate all that, and wit…

Post by randomdata » Fri, May 04, 2012, 4:16 PM UTC

e28eta wrote: post #16

I agree that for some people, RubyMotion may be better than ObjC. I'm not one of them. Regardless, I think your Ruby code examples could have been better chosen: - I'm a huge fan of Ruby's || operator, but probably wouldn't use it to dequeue or create a table cell, because the line is way too long. Perhaps this is fixable with a return after the || - creating labels programmatically seems like a poor example because…

    #define MSTR(...) [[NSString stringWithFormat:__VA_ARGS__] UTF8String]
    
    @implementation LotsaLabels

    - (id)initWithFrame:(CGRect)frame
    {
      if (self = [super init]) {
        CGFloat offset = 0.0;

        [@[@"label1", @"label2", @"label3", @"label4"] enumerateObjectUsingBlock:^ (id object, NSInteger idx, BOOL *stop) {
          object_setInstanceVariable(self, MSTR(@"%@_text", object), [[UILabel alloc] initWithFrame:CGRectMake(0, 10 + offset, self.frame.size.width, 40)]);
          object_setInstanceVariable(self, MSTR(@"%@_label", object), [[UILabel alloc] initWithFrame:CGRectMake(0, 55 + offset, self.frame.size.width, 14)]);
 
          UILabel *text = object_getInstanceVariable(self, MSTR(@"%@_text", object));
          UILabel *label = object_getInstanceVariable(self, MSTR(@"%@_label", object));
 
          text.font = [UIFont fontWithName:@"Arial Rounded MT Bold" size:40];
          text.textColor = [UIColor redColor];
          label.font = [UIFont fontWithName:@"Arial Rounded MT Bold" size:15];
          text.textColor = [UIColor grayColor];
 
          text.text = label.text = [object capitalizedString];
          text.adjustsFontSizeToFitWidth = label.adjustsFontSizeToFitWidth = YES;
          text.backgroundColor = label.backgroundColor = [UIColor clearColor];
          text.textAlignment = label.textAlignment = UITextAlignmentCenter;
 
          [self addSubview:text];
          [self addSubview:label];
 
          offset += 90.0;
        }];
      }

      return self;
    }

    @end

Post by tommy_m » Fri, May 04, 2012, 4:17 PM UTC

Post by poutine » Fri, May 04, 2012, 4:20 PM UTC

cmelbye wrote: post #27

poutine wrote: post #19

- Objective-C is Hard to Use It has a much steeper learning curve than Ruby for sure, but once you're proficient it's no harder to use. Indeed there's benefits to both languages. - Xcode is Unstable It's gone through periods of instability. But in the current version you may encounter the odd crash (perhaps once a week in full time use for me). Really not an issue given it's a cutting edge tool that's rapidly evolvin…

All of these points are subjective, why are you trying to argue against them?..