This thought just popped into my head and I consider the worthlessness of the media pad...
We know Apple sometimes like to go evolutionary towards an end goal. Could this just be an evolutionary step towards a true tablet running Mac OS X and now the iPhone OS? They may want to see how this product would be received before turning towards the true tablet development.
Customer acceptance is certainly part of it. But there are other pressures such as competition. The evolution may also be limited by technology, component availability, cost, and time for software development.
Also, I am not sure that a "true tablet" needs to run OS X. If goal of such a device is "utility" then the less intrusive (and visible) the OS is, the better!
Some of you guys really need to think hard about what you're asking for. Do you really want to try using the standard OS X Photoshop, Final Cut Studio, Excel, etc. on a small-screen (by desktop standards) device, with no mouse or keyboard, limited RAM and CPU, and low power requirements? It just wouldn't work well, if at all. Cocoa Touch is not where it needs to be in its current iPhone implementation, but it's a lot better suited to this stuff than desktop OS X is. Don't underestimate Cocoa Touch (ie. "iPhone OS"), it can be very powerful with a few additions (which Apple is adding all the time for the iPhone anyway). All the great iPhone apps already demonstrate this power, and some potentially great apps are only held back by the iPhone's small screen and limited power, and AT&T's network restrictions, which the tablet device will probably improve on dramatically.
A tablet running standard desktop OS X is a horrible idea. I used to think I wanted that, but I changed my mind after thinking it over.
First, let me say this: If all Apple wanted to do is release an iPod Touch with a 10" screen, the could have done that a year ago.
I agree with this:
Cocoa Touch for the iPhone ≠ Cocoa Touch for the Tablet.
But, the way Cocoa Touch is implemented on the iPhone shows that Apple had expansion in mind. Sure, some things were eliminated, to reduce overhead, but the basic OS X structure is there.
For example:
-- iPhone OS X (Cocoa Touch) supports Windows and Views. Why? There really aren't any [uses for] windows on the iPhone display!
-- The iPhone TableView API uses single-column tables (scrollable lists, actually). This makes sense on a small display. For a larger display [and more powerful device], the Cocoa Touch API could include the multi-column TableView API from Mac OS X.
My last points:
-- iPhone OS is a full OS, with multi-tasking. In fact it is far superior to what we had on the Mac, prior to OS X.
-- Apple pulled some key Mac OS X developers off Leopard to assure that the iPhone OS X was ready for the initial release. It has been said that the iPhone gave these developers the chance to re-implement some legacy Mac OS X code and "Do it the way it should have been done".
-- the migration of knowledge and function (Frameworks and APIs) between Mac OS X and iPhone OS X is a 2-way street.
*