Alright, first, this subject has been covered to the point of being beaten to a pulp all over the web. I won’t repeat it all but I would recommend John Gruber’s rather even-handed posts on the matter The Flip Side of the Multitasking Argument and One App at a Time for the full background and arguments.

Though I see the concerns that other’s have, I simply do not care. It doesn’t effect me. This is partially just my own selfish churlishness as I have no pet projects that require anything that’s missing from the current incarnation of the SDK. My crappy projects will work just fine…

However, it’s also partially because after 13 years of “professionally” programming I’m used to constraints. The business I’m in can be more defined by the constraints than the opportunities. You learn to live with it. I’m so used to hearing the phrase “You can’t do that” (in a variety of interesting accents) that it really has virtually no impact now. This phrase just means I need to modify my approach to solving whatever problem I’m working on, find a different approach or that I need to sell my current approach better to those saying no… This applies to hardware and software interfaces where the party saying “no” is the vendor of those interfaces and it applies to the VP down the hall. The “no” can have good reason or it can just be a result of lack of thought on the other side. Either way, it tends to serve simply to drive more creativity at solving the problem.

There’s already a large community of iPhone developers that won’t take “no” for an answer, thus the large hacking community. I’m not likely to join them (just don’t have the time), but I appreciate and applaud their efforts. For my part, I’m sure the SDK will evolve and respond to developers needs like every other SDK ever published has.

A common refrain from a former boss was “it is what it is” - meaning that there was no sense in complaining about how much “it” may have sucked, we just had to make it work. And we always did…

Geek //