So let’s consider it. The programming tools are radically better, the user interface paradigm is radically different, and the iPhone itself is somewhat of an improvement on 1980s technology.

Typical time to run an end-use model forecast of 20 years in the 1980s was on the order of 1 hour of CPU time on an IBM System/370 model 3081 mainframe. That 3081 had a pair of processors with a cycle time of 26 nanoseconds — about 38.5 mHz — with up to 32MB of main memory. The iPhone 3G S has an ARM processor running at 600 mHz, along with a powerful GPU, and 256MB of RAM. So processing capacity probably won’t be an issue.

Power consumption? The 3081, depending on the model, drew between 23 and 38 kilowatts in operation. The iPhone runs on a battery, and charging it from a USB connector can draw a max of 2.5 watts.

More to come…

The experience of unpacking Apple gear is well-known to be awe-inspiring to people who like that sort of thing – but for most of us the simplicity is what appeals.  Unpacking the HP has left only a single significant memory:

Stickers!

It was covered with peel-off plastic stickers, hard and annoying, but not impossible to remove. It’s not hard to understand the reasoning behind the stickers, but to leave your customers with stickers! as a lasting first impression can’t be the desired result.

There’s a lesson here for application developers.  As with the hardware, the display of logos and branding information is done differently in the OS X and iPhone worlds. You spend a lot of design effort on your application icon, to get distinctive perspective and lighting that fits consistently with the other icons in the dock.  It does not look like your XP or Vista icon. You put the large version of your icon in the About MyApp window with some credits, perhaps to your developers and to other third parties whose frameworks and code you may have used. You add links to your website under the Help menu, along with video tutorials and other material that show your commitment to the Mac.

You do not ever, under any circumstances, waste main window space with a big, colorful and distracting icon, branding messages, or advertisement. Minimalism is a good thing on OS X. If you are very subtle, a subdued version of your icon, with little to no color, can appear transiently during longer operations or idle time, with an obvious way for the user to make it go away – like the gray Apple icon in the iTunes toolbar display.

On the iPhone you minimize by targeting your audience so specifically that your icon is everything you need – unless the user asks to see more, or you have a free app and are upselling to a paid app.

If you are designing a game – never mind.  Different set of rules, discussed on another day.

The answers are “It’s not” and “It won’t.” You may not like the answer, but that’s how it is. There’s no disrespect meant to Windows coders – you could reverse the questions and you would still get the same answer – at least today.

There’s a natural human tendency to understand new things in terms of things we already understand. You can see this when you introduce widely experienced coders to  OS X; every time they see something that looks familiar, they’ll say “Ah, OS X works just like fill-in-the-blank.” That’s a trap that will mislead even the best: coding for OS X is not like anything you already know.  Well, unless maybe you were a NextStep or  SmallTalk coder, but even those only help in a general way.

Actual question from an actual Windows coder: “What’s the OS X equivalent of the Windows registry?”

Actual answer: “There is no registry.”

If you can get your head around that, you will start to learn, Neo…

Right now, we don’t have a lot of the content we anticipate placing here, but we’re done with fooling around and ready to launch again, so here we go…