Originally Posted by ConradJoe
As I said before, some software will be rewritten from the ground up and will likely work great. Some will not be rewritten, and will work OK. Some will not be rewritten, and will work like crap, and will fade into obscurity.
It has happened lots of times before. With 3.1, with 95, with NT, XP and Win7.
There is a big difference between being able to use existing software and being able to optimally use the entire OS interface/paradigm. Legacy stuff will likely work, or most of it will mostly work, anyways. New stuff will work better. The best of the new stuff likely will work best.
I guess, but there's a lot more work and thought and care and planning that goes into the transition from mouse to touch than from various iterations of Windows, the user facing portion of which involves little more than UI chrome.
Apple has approached this by keeping iOS a separate entity (in concept if not code), leading by example by providing best in class tablet software (iWork, Garage Band, etc.) and developing a robust and deep touch lexicon, with developer tools that strongly encourage consistency of that lexicon across apps. To achieve that level of uniformity and integration they've had to be disciplined, taking clear stands on what the iPad is and is not and how it does and does not work. The results speak for themselves.
MS appears to be suggesting that they can have their tablet cake and eat it too; that they can leave things kind of undefined and open to interpretation and still get a nice tablet ecosystem, even while providing a convenient fallback into Windows. I really question that strategy. You look at all those Windows programs with their various and eccentric ideas about UI (including a lot of Microsoft's stuff) and imagine how that works when you're talking about touch on a tablet, which is far less forgiving of random ideas that change from app to app. The iPad feels of a piece, that aren't many jarring moments when you launch an app and wonder where you are. I fear that that might not be the case with Metro apps, and that's going to impact the desirability of the device.
I'm also still really curious about how the Metro language works for anything other than things like social network feeds or browsing. Everything I've seen seems to emphasize the coolness of live tiles and sliding panels and nice typography; can't see how that serves a Metro Word, should that ever come to pass.