That’s the gist of this article.
On average, running Javascript on a device that fits in your pocket seems to be slower than on a machine with a dual-core Intel processor, a bucket of RAM and all the gubbins that go with it.
This is not news.
Now, it continues that running native code on the iPhone is much faster than javascript and this is another reason why developers want an SDK.
Yes and No.
Faster processors allow developers to get sloppy. wouldn’t it be nice if people could just use slower processors or processors optimised for saving power and still get amazing performance?
There are lots of reasons an SDK is not available. All of them good. It’s only a matter of time, however, until Apple can be sure that it’s ready for prime time.
Let me ask you a simple question: If you have a desktop web application that takes 1/10th of a second to do some work, how much time is it going to take for that same application to run on the iPhone?
Only an idiot would think that the iPhone is faster than a desktop. But smart people would want to know that the 1/10th of a second translates to 8 seconds when running on the phone.
-ch
What’s that got to do with the presence or absence of an SDK?
Does anyone have doubts that javascript is going to be slower than native code?
Did anyone think, before the article was published, that the iPhone would be better or worse than a dual-core iMac in javascript performance?
Would anyone deploying an app on iPhone not perhaps test it on a production model (and if they can’t get one themselves, they can avail of a few thousand willing beta testers out there).
So again, why does this mean an SDK for native code is more vital than ever?