iPhone Centre

I was all set to give this week's column over to a new register-direct implementation of a JavaScript interpreter that's many times faster than all currently available implementations. It's not exactly growing hair on a billiard ball, but a nitro-boosted JavaScript will put a shine on AJAX and keep my most beloved language on track to becoming the gold standard for dynamic languages.

Don't look now, but your mobile phone is out to get you. This deadly device can cause accidents, give you cancer or even kill you, according to a rising chorus of alarmist reports.

Apple apparently chose the best possible template for its iPhone developer programs: its own Apple Developer Connection for OS X. Why it then made the iPhone SDK confidential even for those who download it for free poses a puzzling contradiction in the company's seemingly open approach to development.

I have no excuses - I should have known better than to let my gadget envy get the better of me. But, with all the new way cool features added to the iPhone 3G and the fact that my existing AT&T plan allowed me to upgrade at US$199, I decided to join the other crazies in line last Saturday afternoon and spend 2 hours to get my hands on a new iPhone 3G. I've spent more than 20 hours since then trying to get it to do what I needed it to do (i.e., synchronize with Outlook, stay charged up for more than a day, not die when I touch a button, etc.) and then I spent another 3 hours yesterday trying to return it. For more about why I now feel like a moron, read on...

With the iPhone 3G launch now a week behind us, it's time to look back and see how the second coming of the iPhone turned out.

Like the presidential seal that vanished without comment from a politician's press podium, the competitive marketing brickbat that Apple flung at BlackBerry -- that BlackBerry's push e-mail works only with Microsoft Exchange, as if Exchange were an onerous burden -- quietly vanished from Apple's campaign.

Is the iPhone 3G worth waiting in line for? Early reviewers of Apple's new smart phone are mostly positive, but they share some common gripes about battery life and two aspects of dealing with AT&T: the service-plan costs and the skimpy 3G coverage areas.

I'm developing mobile applications -- for the iPhone. Considering all of the mobile platforms available to programmers, why would I select the development platform for the Apple device when I could have chosen Symbian, BlackBerry, or Android?

I've used iPhones and I have an iPod Touch. I love the interface, and I dig the device. Initially, I had to resist the urge to just buy an iPhone and deal with these problems, but I didn't, opting to get a Nokia N95 instead. A year has passed, and I've realized that I definitely made the right choice -- the limitations of the original iPhone (and the iPhone 2.0) are simply too numerous. Perhaps I've been spoiled by my N95 (and truth be told, I'll be getting an N96 in the next few months), but no matter how you slice it, I've decided that the iPhone just isn't my cup of tea. Here's why:

In the 1984 cyberpunk novel, Neuromancer , author William Gibson describes a future in which people can acquire knowledge by buying special chips called "microsofts" that plug into a surgically installed jack behind the ear. Once you plug in the chip, your brain can access its database and - voila! Knowledge!

All evidence points to the fact that smartphone viruses will be a threat to your network even though they aren't at this moment. After all, the latest mobile devices are packed with more and more applications and corporate data, are enabled for real Web browsing and online collaboration, and can access corporate servers. What's more, they live outside your firewall and often make use of three wireless networks (Bluetooth, Wi-Fi and cellular).