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 489826
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by marcp
by henderson101 on Fri 16th Sep 2011 11:57 UTC in reply to "Comment by marcp"
Member since:

I don't really get it. Will they drop flash in favor of Silverlight and HTML5, or latter alone?

The former... well, not, it's not quite that clear cut. Silverlight and Windows Presentation Foundation (WPF) both use XAML as their GUI markup language. Silverlight is a web oriented implementation (akin to "Flash" and "Flex"), while WPF is a desktop oriented framework. Both Silverlight and WPF share an awful lot of basic functionality - it's just that Silverlght doesn't attempt to use the baggage of "desktop" metaphor. The actual UI code can look very, very similar (it being an XML based markup.) On the programming side, again, Silverlight is sandboxed and has a limited access to certain operations (like file operations, etc - basically, stuff you would never want a browser based plug-in to access or have as a capability.) But, really? An experienced .Net dev can jump on to Silverlight reasonably quickly, especially if they have some exposure to WPF, rather than just classic WinForms.

So, what have Microsoft actually done? They have created a middle ground solution, based on the same technologies as Silverlight and WPF. XAML for the UI, and the use of the basic runtime (wrapped up) in a similar way to the way C# apps currently work. They've extended this to allow Javascript and C/C++ interoperability... NOT COM, something new - "projections" - which are API wrappers that present a version of the API to the programmer in a fully seamless way (as if it was part of the usual API.) They've also decided to make most API calls asynchronous, and make creating/calling async methods trivial. The UI "Metro" is wrapped up and presented through this mechanism. All of this falls under the banner of WinRT.

If it's about replacing flash with silverlight ...

No - it's more like "here is a new way of accessing the API and your legacy Win32 style API is effectively dead outside of the classic desktop."

Silverlight is, has always been, and never was anything other than a subset of the .Net CLR.

Silverlight is no way better than other plugins. It's still closed as the gates of heaven and hell.

Silverlight is at least a fully modern and multithreaded platform - akin Java's Applets from a browser perspective. Flash is a horrible hacked single threaded pile of crud. When you use Flash outside of the nice streamlined Flex framework, you quickly realise how inappropriate the Flash plugin is for anything more than banner ads - indeed it's pretty astounding that it even made it this far. (the raw Flash API talks about movies, scenes and such - it really was designed for something else entirely...)

HTML5 alone - yeah. Go for it, but NOT with this terrible, tablet-only, counterintuituve interface called "Metro".

No, that's not what you're getting. Metro API is accessible to any supported language through WinRT. It's not "HTML5 only" at all. In fact, it's not even "tablet only" as the Metro UI is slated to be the "main" UI for Win 8 - at least for the "start menu" style app selection.

Reply Parent Score: 3