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 489720
To read all comments associated with this story, please click here.
It does make sense
by joshv on Thu 15th Sep 2011 16:17 UTC
Member since:

When you think about it, this makes a kind of sense. Currently the plug-in architecture is pretty agnostic. It allows basically any DLL which supports the right API to take over a section of the browser canvas.

Now Metro it appears is entirely legacy free. Nothing you see in Metro depends on the win32 API as we know it. So running IE or any other browser in Metro, you can't just allow Adobe's flash player to load as a plug-in. You'd need most of the win32 API to support it, and that's gone in Metro.

Now that doesn't explain why IE won't support a new WinRT plugin architecture. I doubt the flash player is closely coupled to win32, and could be ported to the WinRT IE plugin API pretty darned easily if such existed. There is no reason not to support a WinRT plugin architecture - and I betcha Microsoft will have to concede this at some point.

Reply Score: 2