|
The article raises the "chicken-and-egg problem -- if no browsers support XHTML 2.0, why write web pages in it? And if there's no web pages written in it, what incentive do browser vendors have to support it?"
If Microsoft wants XHTML, then they will make IE support it, and they will make ASP.NET able to generate it. There will be no need to wait for apps to be built.
On the other hand, if XHTML is not part of Microsoft's strategy, then I don't quite see how it will achieve widespread use.
Is this analysis too simplisic?
|