|
None of the posts touched on the very real and beneficial concept of using XML/XSLT to transform XHTML documents into other XHTML documents. This is a great advantage when you have a group of designers creating the pages and the data is to be populated later from a back end or the page needs to be localized. There are also benefits in scripting and CSS because in HTML you don't need to close the tags so the browser is guessing where the end tag is. This guesswork can throw off CSS calls and script calls and cause the developer extra work. While HTML CAN be well formed there's no good way to verify that it IS well formed. Tidy and widely available XML tools make it easy to validate and check XHTML files for errors.
I don't understand how some developers will say "Well I can create well formed documents with HTML" and then go on to bash XHTML. If you can create well formed documents then what is the problem with using XHTML. It's not complicated, it's not rocket science. It sounds to me that the lazy people aren't on the XHTML side of the argument but on the XHTML-haters side.
|