3 ms·
I don't think mere MVC(in the general sense) implementation will do the trick. The problem with Native App Development is threefold: 1. Is not Cross-Platform:
by realrocker 14y ago
I don't think mere MVC(in the general sense) implementation will do the trick. The problem with Native App Development is threefold:
1. Is not Cross-Platform: Web Developers are comfortable with their code running everywhere without even thinking about it.
2. Has limited access to hardware libraries: Same as above, the developers doesn't need to worry about the hardware.
3. Uses statically Typed Languages: Web Developers who would rather code in PHP, PYTHON, ROR, JS are forced into the intricate worlds of Objective C, Java & C/C++.
The problems with HTML5 are more real. The necessary tools are just not there.
- randomdata 14y ago> 3. Uses statically Typed Languages Objective-C is kind of an odd duck there. I think for all intents and purposes, Objective-C can be treated as a duck-typed language and shares many of the same conventions as Ruby, given their shared Smalltalk heritage. Consider the following code: NSString *string = [NSArray arrayWithObject:@1]; [string isKindOfClass:NSArray.class]; // Returns true Which compiles and runs just as you would expect the equivalent Ruby code to: string = [ 1 ] string.kind_of?(Array) # Returns true I would even argue that Cocoa (Touch) shares many similarities to Rails. Someone coming from a Ruby on Rails background should feel right at home on iOS, though perhaps less so on other platforms.