Microsoft has reported that they fixed silver-light but haven't actually released the fix (for the latest report that I'm assuming you're referring to that was posted on HN yesterday).
Correct. Silverlight 5 is still in beta. They said that they had fixed the issue and will be part of a future release -- of a product that is currently in beta. You typically don't rush out fixes for beta versions of products.
You're missing the point - if it's a fundamental architecture flaw that cannot be fixed, then Silverlight in its current (beta) form suffers from the same problems.
You typically don't rush out fixes for beta
versions of products
You can find fixes of open-source projects as soon as they are committed.
Microsoft made a bold claim, people are curious about how they fixed Silverlight if indeed they did that. If not a new Silverlight release, than at least write some kind of blog post explaining what's different in Silverlight.
But I'd bet this is typical of Microsoft; right hand, meet left hand, please communicate :)
> You can find fixes of open-source projects as soon as they are committed.
That might be relevant if it wasn't for the fact that Silverlight is not open source. They are under no obligation to show/blog their fix until they actually release. In fact, they would probably want to withhold it as long as possible if their intent is to damage WebGL.
If it's typical for Chrome, a web browser with a hefty market share, and we're discussing Silverlight, a web technology, it seems highly relevant. If Google can release frequent beta updates to a web technology product with potential GPU-related security holes, why not Microsoft?
