On Apr 26, 10:03 am, Casper Bang <[email protected]> wrote: > Do we all agree that the sole reason behind sticking with Obj-C is > exclusivity rather than performance?
No: iPhone OS is built on Mac OS X which is based on the old NextStep which used Objective-C. This allows for easy skill transfer (Mac -> iPhone), less OS maintenance cost and common tool chain. Microsoft, for instance, now has three totally separate OS stacks - "Windows 7" for desktop/server, Windows Mobile 6.5 and Windows Mobile 7. The "exclusivity part" comes in when Apple banned cross-compiling. > Hell, Android still kicks butt even if we have to wait another month > or so for the JIT'er to be turned on in 2.2/Froyo. Add to that, the > benefits of sandboxing which you've gained by virtue of the managed > platform. iPhone OS has sandboxing and a runtime, too. For instance, you can't get a NullPointerException on the iPhone because you send an object a message (as in Groovy, you can handle non-existing methods for something like a dynamic finder method), and the runtime just ignores sending a message to a "nil" object. Of course, you'll get "BAD_ACCESS_ERRORS" when you didn't retain an object and it's memory was already freed. ;-) -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
