Why baseball benched Microsoft Silverlight
news.cnet.com
news.cnet.com
The whatwg draft is really quite interesting...
http://www.whatwg.org/specs/web-apps/current-work/#video-and...
In practice everyone will support h264, because terrific implementations ship with OS X, Windows, and Ubuntu (at least once you check the "I am not gnutarded" box). If the BBC's Dirac project doesn't flame out, that could end up being a specifiable free codec. Theora is not remotely viable.
https://developer.mozilla.org/En/HTML/Element/Video http://www.bluishcoder.co.nz/2008/04/firefox-html5-video-wit...
(Extra credit for the word "gnutarded".)
Another issue with H.264 playback is the licensing costs. According to the mpegla website, after 31st December 2010 content producers will have to pay money just to stream content, let along decode or encode to H.264.
AFAIK, Dec. 2010 is when the current licensing agreement expires and a new one is drawn up. They merely reserve the right to change the agreement to add a fee; they don't say that they will.
If you run a website where users pay to view h.264 videos, either by title or by subscription, you need to pays fees per video if you reach a certain number of viewers. Note that these fees are payable now, there is no grace period for this.
For streaming of videos where the end user does not pay (eg. YouTube style services) the terms state:
"In the case of Internet broadcast (AVC video that is delivered via the Worldwide Internet to an end user for which the End User does not pay remuneration for the right to receive or view, i.e., neither title-by-title nor subscription), there will be no royalty during the first term of the License (ending December 31, 2010), and after the first term the royalty shall be no more than the economic equivalent of royalties payable during the same time for free television."
Free internet streaming is therefore covered by the grace period, but lists the payments required after that as being no more than the equivalent of that for free television - the costs of which are listed in the document.
So it seems that in some cases (subscription video) you do in fact have to pay fees now.
And in the free internet streaming cases the wording does suggest there will be a cost. It is certainly possible they could decide to make such usage free. This is far more likely to happen, imho, if there are alternatives to h.264 to enable content producers to negotiate the fees with mpegla.
Currently if you are streaming h.264 on your site, you're taking the gamble that mpegla won't want a cut of your profits post 2010.
The licensing regime is bound very tightly to the enforceability of software patents. It turns out that distributing source code doesn't constitute patent infringement -- it's a description of the invention, something that should be contained in the freely-distributable patent filing. Even then, you can always distribute binaries from countries where such patents are invalid.
For people who want to use non-proprietary formats, or don't want to pay licensing fees for videos they provide. There should be a way for these people to use video on the web. Even if it remains only a niche usage, and at least provides some leverage to reduce the licensing costs of other formats.
Bowman: You see several things. You see a high-grade product that's in some form on 99 percent of the browsers. You've got something that's got mass usage. Secondly you see with Adobe a company committed to the customer experience in video with the Flash Player. We see a partner that continues to invest in their product. They have the same desire that we do. They want the Flash Player to be the best thing anybody has ever seen and we want that. When you partner with people like that, it's not a philosophical discussion. We know where we want to be now how do we get there.
So once we filter out all the market-speak it pretty much boils down to that Flash has a better market-penetration.
Hopefully they'll add threads to flash sometime in the future, that is the most limiting factor facing it today.
download -> componentA > componentB > ComponentC
whereas it might be easier to just go:
CompnentA(file.download());
instead of file.Download (CompACallback, FaultCallback);
Microsoft could drop Silverlight with little impact on the company -- it's not critical to the success of Windows at this point.
Flash has 5+ years headstart than Silverlight. Flash has also seen its share of technical issues and limitations.
With regards to penetration rate, most PCs come with Silverlight pre-installed so this won't be much of an issue in the future.