khelloworld

I don't even own an iPhone. I hope that answers your question.

Gizmodo not only ruined it for Apple and the engineer, it also ruined the fun for Apple fans like myself anxiously looking forward to the rumored-filled days just before the next device unveiling in June. :-/

If anything, I think it will encourage private enterprise to work harder.

I speak objective-c. I like it's verbosity. I couldn't care less about the recent changes in the toc partly because I knew this was coming.

To put it succinctly: All of us are royally screwed.

Yes.

Of course programming isn't just about using APIs. But, writing apps for the iPhone is.

I'm sure they've learnt their lesson from last time. We all know how that went. lol..

I think what you mean is "productive" not "creative." If thats what you mean, I am with you. Obviously the more abstracted out low level details are, the more easier it is to churn out code, thus making you more productive.

But, given that you are using the same APIs (or using wrappers that utilize the same API, which is the same thing), I fail to see how you can do things differently in Scheme or some other language that you couldn't do in objective-c.

As much as I'd like to agree with you, that is simply not going to happen. Do you seriously think companies/developers like EA, Cultured Code, Omni Group etc are going to leave the app store just because apps written in Scheme or Actionscript or .Net are not welcome on the app store?

Again, as much as I'd like to agree with you, none of the prominent app developers are going to be leaving anytime soon. And, as for people who make Farting apps, they probably wont care anyways because use Objective-C or Actionscript, the apps are rather simple anyways. The efficiency of writing code probably wont matter to them.

I'm not really sure if they are hurting themselves.