Anyways, the point of this is that I got an objective C book so that I couldn't finally spend some time on it and it does in fact suck. For me, its simply too verbose and the NS (NextStep), camel case bullshit kills it.
That plus Xcode is so freakin awful. I thought an apple designed IDE would be refreshingly better. Turns out not to be the case. It makes me miss eclipse. Apple seems to be losing it to me anyways. Just look at the non standard interface for the new app store and the new itunes. I think the only reason they are generally successful with design is they cut out features until there are very few things to add to the design. Of course its easy to have a clean interface on something that only has a few options. I guess Xcode is an example of what they do with a larger, complicated application..
Xcode gets to the point where you have ~10 windows all open and even have to drag between them to accomplish stuff. And yes, I can remember all the keyboard shortcuts to bring the different parts I want to the front but its still a cluttered mess.
Enough with Xcode, this was supposed to be about objective C.
Well here is an example of my point about objective C. Several language comparisons of making arrays.
Objective C
NSMutableArray *items = [NSMutableArray arrayWithObjects:@"One", @"Two", @"Three"];
Javascript
var items = ["One", "Two", "Three"];
PHP
$items = array("One", "Two", "Three");
Perl
@items = ("One", "Two", "Three");
Java
String[] items = {"One", "Two", "Three"};
C#
string[] items = new string[] {"One", "Two", "Three"};
Ruby
items = ['One', 'Two', 'Three']
Thats not fair. Those are string in my example and you are using integers. They all would be small with integers.
a < - array (1, 2, 3)
Yikes, it cut my R code out.
And in R
a
Yeah, the superset-of-C syntax craziness is pretty unbearable, and they haven't even allowed garbage collection to be turned on in iOS apps.