A pro-Apple, anti-Microsoft article from Gruber? I'm shocked.
However, even though this is yet another iteration of his "Why <insert Microsoft technology here> sucks compared to <insert Apple technology here>" theme, I tend to agree with him this time.
I cannot imagine the iOS devices finding success if they were actually just Macs with a new category of touch apps strapped on. This only leads to market and developer confusion. If it's just one platform, what is my target device as a developer? If I develop to touch-driven HTML5+JS, why would anyone want to use it with a mouse? If I develop to WPF, why would anyone want to use it with multi-touch? Whatever they call it, it's two platforms, crammed together, and they just don't fit well. As a developer, you still have to make a choice, and it is the device itself that determines what development path you will take.
Then there is the hardware requirements. Windows 7 made great strides in this direction, but I just cannot imagine Windows 8 running as efficiently on an ARM-based device as iOS does today. I hope to be surprised here.
I cannot imagine the iOS devices finding success if they were actually just Macs with a new category of touch apps strapped on.
Maybe we'll see with Lion. :-)
This only leads to market and developer confusion. If it's just one platform, what is my target device as a developer?
How would people want to use it? In some cases you may even do two apps, although you probably could share code (not clear what the app model is for Win8 still). Just like today you might build an app just for OS X, or just for iOS, or you might build one for each. Depends on the app.
Then there is the hardware requirements. Windows 7 made great strides in this direction, but I just cannot imagine Windows 8 running as efficiently on an ARM-based device as iOS does today. I hope to be surprised here.
No idea, but if WP7 is any indication, they are killing perf. WP7 flies on relatively weak hardware. On old SnapDragons it kills the perf of Android on dual-core modern SnapDragons. I hope Win8 has those chops.
The new touch interface looks interesting, but backwards compatability is baggage that threatens to make the Windows 8 user experience an ugly inconsistent mess.
Touch is great for mobile apps, but it doesn't beat the old mouse + keyboard when it comes to desktop productivity.
This discussion reminds me of arguments from the "Raymond Chen Camp" [1]. Backwards compatibility is of huge value and importance to Microsoft, but it's a big burden to carry as well. Throwing away all the code that has been developed to date for Windows would be a fatally stupid mistake.
Microsoft would be better served by keeping their touch based phone / mobile platform seperate from the desktop. I don't think it's possible to build a platform that nicely mixes UI metaphores.
However, even though this is yet another iteration of his "Why <insert Microsoft technology here> sucks compared to <insert Apple technology here>" theme, I tend to agree with him this time.
I cannot imagine the iOS devices finding success if they were actually just Macs with a new category of touch apps strapped on. This only leads to market and developer confusion. If it's just one platform, what is my target device as a developer? If I develop to touch-driven HTML5+JS, why would anyone want to use it with a mouse? If I develop to WPF, why would anyone want to use it with multi-touch? Whatever they call it, it's two platforms, crammed together, and they just don't fit well. As a developer, you still have to make a choice, and it is the device itself that determines what development path you will take.
Then there is the hardware requirements. Windows 7 made great strides in this direction, but I just cannot imagine Windows 8 running as efficiently on an ARM-based device as iOS does today. I hope to be surprised here.