XHTML was the new black a decade ago and a lot of loud people said it was the best thing since sliced bread. Even though it wasn’t half bad, it had one important culprit: it was allowed to be served as text/html instead of only application/xml. There are many reasons for that design, the main one being that Internet Explorer doesn’t support application/xml which would break the web for most people.
Entries with tag xhtml
ASP.NET has been taking a lot of hard words since its inception. Most of the complaints are well deserved, but there are some ways to make things slightly better.
While people are struggling with understanding most of .NET Framework 2.0, the confusingly named .NET 3.0 came along and added interesting stuff to the never ending pile of things to read. Well, it doesn’t stop there. You think that Web 2.0 is hotter than Scarlett in a burning Sambuca? Well, I got news for you.
If you have followed the crowd and abandoned HTML for XHTML, you may have noticed that some elements needs to be closed in your markup. The reason is that XHTML is simply a reformulation of HTML in XML syntax. It’s a subtle but very significant difference between HTML and XHTML.