Having just watched Revenge of the Electric Car recently, they came very close, to the point where they almost couldn't make payroll, and were only saved by Musk handing over the last of his money, which was basically completely gone because he had already dumped it all into Tesla and SpaceX. If the documentaries depictions of events (and the things Musk says in the documentary) are to be believed, the company came within inches of blowing up, and they did have layoffs. These days, they're in far more favourable shape (in terms of resiliency) than they were back then.

Right, but an ATM card fits in my wallet. A USB stick doesn't, although something like one of those SD cards with the built in USB headers might.

That would work, but it now requires me to have a specific USB drive on me when I need to get a file. That's not always guaranteed in the "Oh, let me just log onto my file storage account on your computer and I'll grab that file for you" situation.

Because unless you're going to memorize your private key so that you can enter it every time you log into the web interface on some computer, you'd have no way to decrypt the data. I presume that you have to move a private key file between any computer you want to use Wuala on? Because if the company is storing both your private and public key on their server, then the client versus server side encryption is moot and it's no better than dropbox (because the company can decrypt your files in either case).

I see a java app, not a web interface.

And how would I then upload or download files via the web interface (assuming that there is one)? Client-side encryption would break a lot of Dropbox's advantages.

They switched to 64-bit PowerPC chips, and then promptly migrated to the Intel Core Solo and Core Duo chips, which are 32-bit chips derived from the Pentium M. They could have avoided this extra transition by using AMD's 64-bit chips for their initial transition, but AMD didn't have any decent mobile chips at the time.

Wow, and I spelled GLONASS two different ways, both wrong.

The iPad 1 and iPhone 4 are definitely not the same target; one has double the RAM of the other, for one thing, despite both using the A4. That can be a rather important difference for something like a game; you're expected to render the game at a higher resolution, but you've got half the RAM to do it in. And furthermore, within those targets that you've mentioned, the clockspeed varies from 600 MHz on the 3GS to 1GHz on the iPad; that can make a rather big different if your app or game is processor-intensive.

The iPhone 4S and iPad 2 are admittedly much closer together; they only differ (apart from resolution) in clockspeed, and then only by 200MHz. But that ignores the fact that designing an interface or input paradigm for the iPhone/iTouch and the iPad is going to require a different approach, or that you're going to have to account for differences in hardware support (the iPod Touch 4th gen might seem a lot like an iPhone, but it has no GPS/GLOSNASS or compass support, rendering any location-based app nearly useless). The iPad has a compass, but only gets GPS on the 3G models, and no GLASNASS in any version.

It's not even true anymore anyhow. There are so many different classes of Apple hardware that a developer has to target that it's not a homogenous platform anymore. You've got three different resolutions ranging from 480x320 to 1024x768 (not even the same aspect ratio), two incompatible instruction sets (ARMv6 and ARMv7), two incompatible and fundamentally opposite graphics APIs (OpenGL ES 1.x and 2.x, which is kind of like DX7 fixed function versus DX9 programmable), varying amounts of CPU cores, clockspeeds, amounts of RAM, screen sizes... Third-party iOS apps are running on three different device families, and that's only going to broaden when Apple's iTV product comes out.

All told, there are currently twelve different product lines running iOS (with further variations within a product line, such as amount of flash), all with different capabilities, all with different OS version support. For each of those twelve devices, you have to support at least two major OS versions, and potentially a few sub-versions. The feature grid on the wikipedia article (http://en.wikipedia.org/wiki/List_of_iOS_devices) should underscore how non-homogeneous the platform is.