Microsoft Tips the Scale In Favor of HTML 5

aabelro writes "Dean Hachamovitch, General Manager for Internet Explorer at Microsoft, has announced that IE9 will use only the H.264 standard to play HTML 5 video. Microsoft seems to have become very committed to HTML 5, while Flash loses even more ground. The announcement came the same day Steve Jobs detailed why Apple does not accept Flash on iPhone and iPad."

Comments

wow

[Anonymous Coward]

for once microsoft do something that makes sense. Though it would be nice to have support for an open video standard...

Re:wow

[delinear]

for once microsoft do something that makes sense. Though it would be nice to have support for an open video standard...

Or, to look at it another way, Microsoft stay true to form and support proprietary standards which put open source competition at a disadvantage...

Re:wow

[cowscows]

Performance aside, why would anyone want there to be a dominate web platform that's controlled by a single company, unless you happen to work for that single company?

Flash has basically been, for the past 5+ years at least, the Windows of interactive/animated/etc. web content. It's a platform that was in the right place at the right time, and was just barely good enough to become a major standard. All this despite the fact that everyone is constantly complaining about how much it sucks, and nobody likes it. And there's not much anybody can do to truly fix it, except for Adobe, and it's taken them years to get it to work decently on any mobile device.

Seriously, does anybody besides Adobe want Flash to become the dominate platform for anything other than little browser games? Sure, Apple and MS are fighting against it for self-interested reasons, but those reasons seem to align rather nicely with what is good for the internet as a whole, which is to have as much be open standards as is possible.

Re:wow

[slimjim8094]

H.264 is perfectly open-source, but patent encumbered. There's a tremendous difference. You do yourself a disservice to confuse the two.

What you're describing would be true if they supported only WMV, but absolutely false for h264.

Re:wow

[ink]

All this despite the fact that everyone is constantly complaining about how much it sucks, and nobody likes it.

That's not entirely true. Graphic designers generally LOVE Flash because of the Flash builder, Illustrator, Photoshop and the rest of Adobe's creative suite. There aren't any tools that I know of that put that kind of artistic power in hands of non-techies. CS5 does target HTML5, but it does so by using the canvas tag and a lot of JavaScript -- not by outputting "native" HTML5.

This is also what puzzled me about Jobs' claims yesterday that the iAds were all done only in HTML5. I know many advertising content creators; not many could pound out raw HTML5 that would be as impressive as the demos for iPhone OS4's ads.

In order to kill Flash, someone will need to come out with a vector-timeline-tweening GUI builder that doesn't require the developer to touch JavaScript. Perhaps Adobe will do this with Dreamweaver, or maybe Apple will release an "XCode for artists" at some point. Until then, however, don't expect Flash to disappear.

Re:wow

[fuzzyfuzzyfungus]

I suspect a different motivation: Silverlight.

Using Flash as a video player is, by a fair margin, the most trivially replaced function that isn't addressed by pre-HTML5 web standards(stupid shit like Flash based menus and random site chrome is, of course, even easier to replace; because it could have been done in standard HTML+javascript ages ago; but that is largely a lost cause). However, that (quite simple) function is also a huge driver of Flash installation. Basically, if you want to watch video on the web, you need to install Flash. Once you have flash, you bolster Adobe's install base stats, serve as a target for much more sophisticated Flash-based applications, and bolster Adobe's efforts(through AIR) and similar to have a quasi-unified webapp/desktop-app runtime based on Flash and their various content creation tools.

Microsoft has its own, competing quasi-unifed webapp/desktop-app runtime, based on .net, winforms, and the like. Unlike AIR, it much more closely ties the user to Microsoft, and Microsoft platforms and technologies. Therefore, they want to destroy AIR and Flash.

By indicating support for HTML5, which will support the relatively trivial video use cases(youtube style stuff, without Serious DRM mandated by paranoid content providers), they substantially reduce the motivation of users to download Flash and corporate IT departments to install and support it. Since Silverlight comes by default in newer MS OSes, they get increased marketshare vs. Flash/AIR.

Since HTML5 makes possible advanced web applications, but still lags in easy tools vs. Flash or Silverlight(which won't stop Google and their ilk; but will stop Joe Flash Monkey, or Bob corporate intranet developer), HTML5 can be safely supported without destroying Silverlight.

That is my theory. Yeah, h.246 as the html5 video codec of choice puts mozilla in a tough spot; but it isn't as though there won't be some workaround(patent violating 3rd party builds, plugin that exposes system codecs, whatever.) in short order. It isn't good; but it isn't a huge threat. I'd say that this is about kicking Adobe while Apple is already holding them down...

Re:wow

[Raffaello]

1. This places an additional burden on open source browsers to keep pace with the underlying platform WRT performance. History shows they will likely lag significantly.

2. This doesn't address features at all. Both Apple and MS will make sure that the HTML5 spec is always significantly less featureful than the native application platforms.

The result will be that the highest quality applications will need to be written to native platforms, not an OS neutral web platform. This means hardware and/or software vendor lock in, which is just what Apple and MS want.

This is Java all over again. MS embraced and extended it. They paid a billion in damages for doing so, but it was money well spent to cripple a potentially game changing, OS neutral platform.

Apple claimed to be the best Java platform bar none. You could even write native cocoa apps in java. Then, when Apple had leveraged their "open standards" act to attract enough developer mind share, they began systematically treating Java as a second class citizen. Launch a java app and get a frightening warning:

  "! The application SuchAndSuch is requesting access to your computer"

You don't get this kind of warning running a native app of course.

And now you can't write cocoa apps using java anymore either. What a surprise.

MS Does embrace and extend. Apple does embrace and marginalize. Same end result.

Apple and MS are not your friend - they want your money. Google is not your friend either, but at least they don't want your money - they want advertisers' money. The lesser of two evils.

Re:wow

[Anonymous Coward]

I don't think "you can look at the source but you need to pay us to use it" is any kind of open-source license since it restricts end-use even though it doesn't hinder distribution. OSI licenses typically include "you grant a worldwide royalty-free non-exclusive license" clause for that reason.

If you meant an open standard with open documentation, and open working group, you shouldn't do us a disservice and confuse the two. They can openly write as many patents, licence fees and international trade restrictions as they want, they do that to avoid members backstabbing each other through selective communication, and to stand together to strengthen the patent position.

It's a Trap!

[amiga3D]

I can't help myself. I had to do it.

Re:It's a Trap!

[camperdave]

It's a Trap!

Yes! It's step one in Microsoft's basic business plan:

1. Embrace
2. Extend
3. Extinguish
4. Profit!

So, the key is to anticipate how Microsoft might extend the protocol, and "head them off at the pass" by releasing Open Source variations as soon as possible.

Although, I suppose it's possible that Microsoft has learned the danger of becoming the defacto standard with shoddy products through its attempts to kill off XP and IE6... but I doubt it.

Re:Goodbye Flash

[arogier]

This says nothing about abandoning flash, just only allowing H.264 video with a video tag.

Unsurprising

[whisking]

It is quite unsurprising they will support only h.264. They are a licensor in the h.264 patent pool (just like Apple) so it does not cost them anything and they actually get money when somebody licenses it, so it makes sense to endorse its use. If something else (theora, vp8,...) will actually win the html5 video format war, they can always add the support later. Obviously I am joking about this part :)

Re:Youtube

[self assembled struc]

using the youtube flash player?

html5 != no flash

html5 is just a version of html which supports a video tag just like an image tag. it also supports the object tag. which means flash works in html5.

the only case where flash isn't going to work is where the operating system or browser does not have a flash plug in.

safari only supports h.264 in the html5 video tag as well. yet, youtube works just fine in it.

mozilla only supports ogg in the html5 video tag. yet, youtube works just fine in it.

Wait, also

[bbqsrc]

Why the fuck is this categorised as Apple? It can't have less to do with Apple. Seriously.

Can you turn it off?

[lfp98]

The major advantage of Flash is that you can choose NOT to install it. With HTML5 decoding built into the browsers, are we all doomed to watch whirlygigs everywhere, all day long?

Re:Goodbye Flash

[Animaether]

Did you just not read the post you replied to, or what?

This says nothing about abandoning flash, just only allowing H.264 video with a video tag.

You can still use Flash as long as there will be a Flash plugin for IE9. There's no reason to think there won't be - so go ahead, just use the object tag as you have been.

The only scale this might tip is the Theora vs h.264 thing as MS announced that as far as the video tag goes, they will only accept h.264 datastreams . Unless this in itself can be extended using plugins, this means a great majority of people who browse the web will be limited to viewing those h.264 datastreams. The significance (closes vs open, etc.) is probably lost on those people, though... so why would Microsoft care to support a second non-industry-backed datastream if there's no push for them to do so.

Follow the money before you rejoice

[c0d3g33k]

This move is as self-serving as ever, so be careful what you wish for as the Flash hate clouds your mind.

1. Microsoft doesn't control Adobe and I'm sure that bothers them. It sure as hell bothers Steve Jobs. So why not take them out while they are vulnerable?
2. Microsoft is part of the H.264 patent pool, so they will make money when the licensing bombs go off. Killing off a competitor (flash) so users and content providers have few alternatives and must pay up puts them right where Microsoft wants them.
3. Once flash is gone (or has greatly diminished influence/relevance), Microsoft is free to tweak things in a way that suits them better. Embrace, extend, extinguish.
4. HTML5 video has no established standard DRM solution which content owners crave. Flash does, so it's hard to get content owners on board with Microsoft's agenda at present. I suspect that Microsoft has something in the works to offer them, which will conveniently be exclusive to Microsoft controlled platforms, or licensable to those who play nice (Apple). Sorry Android (and Linux).

This makes me very nervous.

Huh?

[mister_playboy]

Given the amount of time it has taken for the Gimp to become a strong competitor to Photoshop...

Are you from the future? I'm a GIMP myself, but come on...

Re:Huh?

[mister_playboy]

I'm a GIMP user myself

Damnit... :P

Re:Only H.264?

[Anonymous Coward]

Dude, you do know that JPEG, GIF, and MP3 are all patent-owned standards too, right?

The patents on GIF have expired. Baseline JPEG (which is what browsers support) is royalty-free. Closed formats are the exception on the web, not the rule.

Re:Goodbye Flash

[binarylarry]

Increasing Silverlight's market share is what this is about.

Basically, Microsoft is going to embrace HTML5 and use it to hurt Flash, it'll then start to phase HTML5 support out once Flash's market share starts to take a large enough hit and talk about how HTML5 doesn't have enough support or doesn't "have all the features our users demand," then it will start to pimp Silverlight, integrated it with the next Xbox and so forth and remove "upgrade" all the devs to their Expression platform for developing Silverlight apps.

#include standard /. HTML5 video corrections

[Paul Jakma]

• HTML5 != video codec

  That is to say, HTML5 is a way to embed video into web pages, along with controls. HTML5 doesn't say anything about the video codec that should be used, similar to how the IMG tag doesn't say what kinds of image formats are supported. Further, the videos that are loaded will almost certainly be in some container format, like Ogg, MP4, AVI, etc.. - not in raw codec data form.

  If the underlying system has a general media decoding system, and if the browser uses that, then the browser will support any kind of media supported by that underlying system.

• HTML5 is open

  It's an openly specified W3 standard. As a means to embed video into webpages, HTML5 video is much better than using the object tag to suck in a proprietary blob to then suck in the video.

• The H.264 codec is openly specified.

  H.264 is openly specified in standards drawn up by the MPEG and published by ISO. There are free software implementations of H.264. H.264 rather is encumbered by patents, the licensing for many of which is administered by the MPEG-LA. The patent situation is what things difficult for distributors/users, there is no lack of standards.

  Note that flash players often use H.263 and H.264 codec videos, and so have all the same patent issues for free software implementations (in addition to the problem of Flash not being fully documented, and not having any complete free implementations).

Re:Goodbye Flash

[javilon]

It is clear that the move is not against Flash, the Flash plugin will always be there.

It is a preemptive move against Google's VP8 in particular and open source in general. Basically they are creating a problem for Firefox (which has stated that they won't support H.264) and trying to stop Google's VP8 before it can be successful.