This is more than just a wind-up: it shows that Microsoft can't attack WebGL on one hand and push Silverlight w/shaders on the other. This puts pressure on them to come up with a consistent message.
Did any of the Microsoft-bashers here even read the article? Microsoft responds in the comments and says the issue is already fixed in internal builds and will ship with Silverlight 5 RTM.
