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 510349
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: I think
by Alfman on Mon 12th Mar 2012 23:51 UTC in reply to "RE[6]: I think"
Member since:


"No of course not, the consumer preview is like a week old. I don't have two sets of code reimplementing the same functionality to link to you."

"However, the facts speak for themselves. It's a fact that the legacy code is not mobile aware, and doesn't give you the breadth of information that the new networking model gives you."

"I'm unsure how any of what I said above is not something immediately obvious. It's a given the old technology doesn't, or most likely can't, implement the new technology features. I then go on to cite said features as reasons for implementing the new technology. It seems pretty cut and dry to me."

I'll give you the benefit of the doubt that you know something your not saying which allows you to say these things. However I was hoping for more solid evidence than "immediately obvious" and "facts speak for themselves", since those are rather empty statements.

You say the networking has mobile cap awareness, but what exactly will apps do that they could not have done in a compatible way with older APIs? Is there really any technical reason that we'd fundamentally have to rewrite our whole application around a new API in order to take advantage of mobile cap awareness? I doubt it very much. I imagine the APIs have more in common than differences, which is why I would have liked to see an explicit concrete counter-example.

Reply Parent Score: 4