The question "who's scared of header files" makes me want to say: Not me! I am not scared of header files. They are just totally unnecessary and get in the way of coding. One more thing I need to think of, and for no reason at all. I am architecting very large systems in Java, I have never missed header files.
I wouldn't mind so much if XCode were an actually good IDE a'la Eclipse or IDEA. Writing a new method would then work like this: 1 - Write it straight into the .m file. It ends up with a warning, one-click quick fix offers to add the definition into the corresponding .h file, done in the blink of an eye. But that's not what XCode does. [Note to Apple: XCode still sucks, there is no excuse, a glorified text editor just isn't good enough, this is not 1998.]
I find obj-c extremely painful but admittedly most of the pain is inflicted by the manual memory management and that's fixed in 2.0. Unfortunately not on the iPhone yet, so I can't use it.
Compared to Ruby there is still lots of code clutter in a typical Objective C class. So I just want to point out why Ruby is superior: Less code means not less typing, but rather a better focus on the function. In Ruby, a source file contains nearly 99% pure function. In the same class in Objective-C, you will see lots of stuff that is irrelevant to the function, things that the compiler wants, funny little symbols, pointers * which you can ignore (then why are they there), its a mess.
by nikolaus — Dec 20
I wouldn't mind so much if XCode were an actually good IDE a'la Eclipse or IDEA. Writing a new method would then work like this: 1 - Write it straight into the .m file. It ends up with a warning, one-click quick fix offers to add the definition into the corresponding .h file, done in the blink of an eye. But that's not what XCode does. [Note to Apple: XCode still sucks, there is no excuse, a glorified text editor just isn't good enough, this is not 1998.]
I find obj-c extremely painful but admittedly most of the pain is inflicted by the manual memory management and that's fixed in 2.0. Unfortunately not on the iPhone yet, so I can't use it.
Compared to Ruby there is still lots of code clutter in a typical Objective C class. So I just want to point out why Ruby is superior: Less code means not less typing, but rather a better focus on the function. In Ruby, a source file contains nearly 99% pure function. In the same class in Objective-C, you will see lots of stuff that is irrelevant to the function, things that the compiler wants, funny little symbols, pointers * which you can ignore (then why are they there), its a mess.