Quote:
Originally Posted by iphonatic
Ever tried to debug JavaScript errors in IE?
M$ should have kept IE in the lab if it ever detoured there on its way from Ballmer's evil lair....
I'm a noob at Obj-C but I'm an Apple fan boy from a while back, ex Windoze engineer.
I've just finished my first iPhone app for a client and encountered lots of problems along the way. Most of them would have been solved with a better understanding of all the API calls/classes, but a few were down to deficiencies in the language and terrible lack of debugging.
When I was reading through dev books as a beginner, I remember seeing warnings about "sending to nil" all the time, but never thought it would happen to me... eek!
That said, I'm about to get back to work doing some PHP programming and even though I can do a lot more functionally with PHP, nothing gives me as much satisfaction as seeing something I programmed running on such an awesome device as the iPhone!
Soon as I can make it financially viable, I will throw a few more eggs into the Cocoa development basket, I love it!  |
Sure, that's why I use Firefox on both Apple and Windows. And Linux. I don't have time to be a fanboy of any environment -- I'd rather be billing on whatever someone wants to pay me for. Really I'm thankful that the iPhone is so commercially successful and the development environment is so antediluvian, it makes for far less competition when bidding on projects.
I think it would be a mistake to dwell on the "awesome device"-ness of the iPhone, at least from the point of view of managing your career as a business. If Apple learned anything from the Newton, it's that technological superiority has little to do with commercial success. The iPhone is the Palm 3 of it's time (I mean that in a good way), and if Apple continues to evolve the platform as slowly as they have, they will get their lunch eaten. One difficulty of this market is that people chuck their phones every two years or so, so a 40 million unit head start doesn't buy you as much as you'd think.
