To view parent comment, click here.
To read all comments associated with this story, please click here.
VfE is just a simple template (an obvious one at that)--it's free for anybody to modify. I won't put Silverlight into it (as before, the plan is to remove things, not add them), but anybody could quite easily add Silverlight to it, I won't stop them.
But a WinMo device should play the MP4 file download anyway, if it supports it. HTML5 video is just literally handing a video file to a browser and saying 'here, play this'. Why anybody would want to then wrap that simple process in a plugin architecture, and framework system, I don't know--especially on a mobile device of all places. Simplicity and the fewest number of levels between the video and the hardware the better. That is why MS don't get the web. HTML5 Video is the solution to video on mobile devices, period. If MS write Silverlight into WinMo, but not HTML5 video they are truly shooting themselves in the foot, and as said before, yet more proof positive that Microsoft are against an open web.
Are you joking? I also love C# (especially), Windows 7, and Office, but I despise Silverlight (when used for video). I wouldn't mind it being used for online games, where it is definitely superior to Flash, but you would have to be out of your mind to use it over HTML5 for video.
So let's cater to iPhone 2.0, but catering to Windows Mobile and IE is an unforgivable sin?
Silverlight and HTML5 video tags really have nothing to do with each other. One is a RIA framework which happens to play video, and the other is simply a mechanism for playing video.
There are obvious advantages on both sides, but claiming that one is preventing the other, or is in place only to prevent the other, is stupid.
Look at the majority of Silverlight apps, they are usually LOB RIAs and not video streaming solutions. That's just one facet of the platform.
It is counterintuitive to suggest that Microsoft is opposed to HTML5 when it co-chairs the W3C HTML working group.
I'm afraid that is just not the case. In fact, MSs past behaviour and their unwillingness so far to implement HTML5 support in IE suggests the it is counter-intuitive to think anything else.
Silverlight shows all the signs of the usual MS behaviour, i.e. their implementation of a partner's technology in a cheap bid to hook more people to their platform. What they are doing with Silverlight is nothing new and has been repeated ad nauseum throughout their history. I just don't understand how people can't see that.
We've heard about Microsoft departments trying to do each other in, and Silverlight / IE is one of those areas of divide when it comes to Microsoft.
I do hope that IE9 is an awesome browser with Canvas, SVG and Video, but Microsoft have committed to nothing other than rounded corners and anti-aliasing; what a joke.
The more IE supports the standards, the more that conflicts with Silverlight which is trying to usurp those standards. This doesn’t sound like a company that understands the web very well.
Instead of making Silverlight at all, they should have first maxed out standards support in IE, then developed professional friendly design tools much like Flash studio that compile into HTML/JS/CSS/SVG and so forth; and anything they wanted to do that couldn’t be met by the standards, implement them in IE only and submit those features to become part of the standards. Both Canvas and Video (and Img by the way) were proprietary first and then accepted by other vendors and turned into standards.





Member since:
2005-11-10
1. I don’t want to help make Silverlight the next Flash.
2. OGG in Silverlight is only good for IE users, and IE users already have Flash.
3. It would bloat the code, and the goal is to make it smaller over time as we ditch layers (QuickTime can go once iPhone OS 2.0 is gone)
By 2012 the smart phone market is going to be a solid part of society. The Olympics are going to be broadcast online using Silverlight. This is inherently incompatible with a lot of smart phones, by which time Microsoft may use this fact to sell a lot of WinMo7 phones.
Microsoft don’t want an open web. They want the same web they had in 2001. Silverlight is their ticket back there by making interoperability require Microsoft at every stage. I’m not going to touch Silverlight with a barge pole.