Linked by David Adams on Thu 15th Sep 2011 07:08 UTC, submitted by kristoph
Windows Microsoft announced during the build conference, and Steve Sinofsky reiterated in a blog posting that: "For the web to move forward and for consumers to get the most out of touch-first browsing, the Metro style browser in Windows 8 is as HTML5-only as possible, and plug-in free. The experience that plug-ins provide today is not a good match with Metro style browsing and the modern HTML5 web." Sinfosky goes on explain why Microsoft will not include Flash and why it's no longer needed. It's as close as we'll get to an obituary for Flash. Update from Thom: Added a note in the 'read more'!
Thread beginning with comment 489754
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Title is slightly misleading
by MollyC on Thu 15th Sep 2011 19:31 UTC in reply to "Title is slightly misleading"
Member since:

This site has a tendency to overstate things in the headlines... and the articles themselves.

For example, IIRC, just yesterday there was an article declaring the Win32 API as "dead" or "the past" or whatever, but Metro apps can indeed make Win32 API calls - albeit only a subset (they can't make any of the Win32 UI or GDI calls for example).

Reply Parent Score: 2

kristoph Member since:

Well, they just said at build that if you bypass the limitations of WinRT (meaning you try to make Win32 API calls other then the designated COM interfaces) Microsoft will not allow you to sell your app in their app store.

So, sure, you can do all sorts of hacktastic things in your code including call the Win32 API but officially this is not something you should do.

And, honestly, why would you want to? The whole point here is to migrate away from the Win32 api to WinRT. Using the Win32 API will mean that your app will break when they make that whole stack optional.


Edited 2011-09-15 19:58 UTC

Reply Parent Score: 2