To view parent comment, click here.
To read all comments associated with this story, please click here.
What you meant to say, surely, was that "unlike other stuff, the document.querySelector from the W3C Selectors API doesn't achieve, in an open standards way, functionality which we wish to be kept as lock-in for Silverlight".
As they say on slashdot ... there, fixed it for you.
Edited 2009-03-26 03:12 UTC
No worries, I've seen your mis-information all over this thread and was waiting for your response.
Browsers are free, no one cares about lock-in...if you don't like what a browser does (as an end user), then move on. If you don't like what it does (as a developer) then don't develop for it, or figure out ways around whatever isn't working for you.
Sometimes I wonder if the only people who jump up and down screaming "standards standards standards" are people who've never actually developed real world web apps, simply because they have nothing better to do.
Have you ever wondered why these standards are still just in 'recommended' or 'draft' standard? Because no one out in the real world of web development cares about them...at least not the ones mentioned over and over in this thread.





Member since:
2005-07-06
Because compared to some of the other stuff, this is actually useful in the real world?