Linked by Thom Holwerda on Sun 11th Mar 2012 22:21 UTC
Windows And thus, Microsoft bites itself in its behind with Metro. As you all surely know by now, the Metro environment in Windows 8, and its accompanying applications, need to follow a relatively strict set of rules and regulations, much like, say, applications on iOS. For one type of application, Metro has already proven to be too restrictive and limited: web browsers. Microsoft has had to define a separate application class [.docx] - aside from Metro and desktop applications - just to make third party web browsers possible for Windows 8.
Thread beginning with comment 510331
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:


There is just too much bespoke software that relies on a desktop interface and .NET and we aren't talking about old version of .NET as recent as 3.5 and 4.0.

Also Try firing up VS (even 2011) and there is no way this fits in with Metro.

I think there will be still a classic desktop, but will just have a much "flatter appearance".

Reply Parent Score: 2

zima Member since:

For now? And probably at least for most of current decade. Kinda like there was quite a lot of ~DOS UIs around, they are still around here and there.

But what I suspect might be at work here: a long(ish) term strategic push, for when the tech derived from MS Surface will be really ready for mass adoption - and, to really work, it would also probably require for its UI something like already fairly refined Metro; something MS probably needs to force a bit, in the meantime.
And in a decade, or maybe only half a decade, I imagine it could give something really awesome... (also useful for many "serious" usages and/or particularly the more creative ones - say, a return of inclined drawing board, as a large touchscreen)

Edited 2012-03-19 00:07 UTC

Reply Parent Score: 2