In a brief discussion about web standards, Bill seems to interpret web standards as ws*, xml, etc. He does not really mention html, xhtml, css or similar approaches, which is why he probably does not follow Molly’s point to sceptics of Microsofts commitment to webstandards.
I’m just saying there are a lot of skeptics still out there.
How can they be skeptical? I guess if your job is to be skeptical, you’d hate to be out of a job!
Roger Johansson follows up on his blog:
No, Bill, that is not why people are skeptical. They are skeptical because they find it hard to believe that the richest company in the world can’t afford to make a Web browser whose Web standards support matches that of browsers created by non-profit organisations, open source projects, and one man bands.
With the release of IE 7, I think that Microsoft has actually showed that it’s browser team is very comitted to pushing web standards to a better level. But there is another issue that — in my opinion — is more important because it affects the hordes of developers using Microsoft technology.
My biggest concern, therefore, is not the browser, but the Microsoft developer tools and their lack of focus on webstandards.
Microsoft tools lack support of web standards
The biggest issue is not IE’s commitment to webstandards, but Microsoft and it’s developer tools’ commitment to webstandards
And no, recent support for xhtml validation does not make your tools entirely focused on webstandards.
I have seen recent books bought by colleagues at work, where every piece of HTML is table based layouts, FONT tags, all capital tags, etc.
So there might be a commitment on the strategic level, but it’s very badly executed. I’d really appreciate if you post a comment with any examples you stumble upon.