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


Can you point to *specific* code examples so that we might talk meaningful comparisons? I'm not going to believe the new APIs are better just because microsoft claims so; they've gone down this path countless times already. So why exactly are the new incompatible APIs better?

Like any other company, even on FLOSS world, the new APIs are always better.

Just look for the sound APIs in Linux or QT APIs in MacOS X, just to cite two examples.

Reply Parent Score: 3