问题描述
XHTML应该是模块化的，但我还没有看到任何服务器端语言可以充分利用的任何。
XHTML也更为严格，我看不出优势。 XHTML提供了什么，我需要如此糟糕？如何让我的代码更好？
编辑：我在评论中发现的另一个问题：XHTML解析速度比HTML快吗？
编辑2：在阅读完所有评论和链接之后，我确实认为另一篇文章应该是正确答案，所以我选择了直接链接到最佳源代码的文章。
此外，还要表明人们在没有阅读的情况下就可以获得绿色评论。 您应该阅读，这是一篇内容翔实的文章，它警告某些XHTML在HTML上的缺陷。
直到我读完XHTML之前，我都非常喜欢它，但它确实提出了一些有效的观点。包括以下内容：
在处理某些项目时，未来的兼容性可能会很大。这篇文章继续写出其他几个优点，但我认为这可能是我最喜欢的。
不要把文章误认为是对XHTML的咆哮，作者的确谈论了XHTML的优点，但在潜入之前注意缺点是很好的。
I wonder why I should use XHTML instead of HTML.
XHTML is supposed to be "modularized", but I haven't seen any server side language take advantage of any of that.
XHTML is also more strict, and I don't see the advantage. What does XHTML offer that I need so bad? How does it make my code "better"?
EDIT: another question I found in the comments: Does XHTML parse faster than HTML?
EDIT2: after reading all your comments and the links, I indeed agree that another post deserves to be the correct answer, so I chose the one that directly links to the best source.
Also, goes to show that people upvote the green comment without even reading it.
You should read Beware of XHTML, which is an informative article that warns about some of the pitfalls of XHTML over HTML.
I was pretty gun ho about XHTML until I read it, but it does make several valid points. Including the following bit;
Future compatibility can be huge when working on some projects. The article goes on to make several other good points, but I think that may have stood out the most for me.
Don't mistake the article for a rant against XHTML, the author does talk about the good points of XHTML, but it is good to be aware of the shortcomings before you dive in.
这篇关于在一天结束时，为什么选择HTML上的XHTML？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！