Linked by Thom Holwerda on Fri 29th Oct 2010 20:48 UTC
Thread beginning with comment 447943
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2005-11-29
I don't think the restricted portions are restricted at all. Simply write a decoder for your favorite open codec, and your problems are solved. They are bridges you'll need to cross with HTML5 anyway, so the pain is unavoidable.
The web is just a tangled mess of garbage, slow progress, and backwards programming models. Silverlight on the Web(specifically as a Flash competitor) was not killed by a lack of openness, it was killed by the stupidity of Microsoft. Silverlight on the Desktop (Full trust OOB) and as a WP7 dev platform, is alive and kicking.
The web needs a massive redesign. It will be on the shoulders of a sweeping, pragmatic, and breaking change. It won't be piecemeal or in any iteration of HTML/CSS/JS. I had hoped Silverlight would be it, but as Silverlight's ex Product Manager put it, Microsoft has a shiny object syndrome, in which it changes focus really rapidly.