By: How Microformats Will Change the Web « Brian Cray’s Weblog
[...] the false perception that there is a bigger cause. It’s just created a lot of confusion. See: 1, 2, 3, 4 for just a few [...]
View ArticleBy: Best Practices » Blog Archive » XHTML versus HTML
[...] I can’t say that either side has done anything to absolutely convince me, but Emil makes a compelling case with his article, Why XHTML is a bad idea. [...]
View ArticleBy: Caracol y Punto » Blog Archive » HTML ó XHTML
[...] http://friendlybit.com/html/why-xhtml-is-a-bad-idea/ [...]
View ArticleBy: Jim Westergren
Hi Emil, Good article and good point. On my latest major site that I am currently building I am using XHTML 1.0 strict – mostly to be prepared for the future. I tried sending it in XML with a similar...
View ArticleBy: Emil Stenström
@Jim Westergren: Nice that you liked the article :) Since HTML5 is the future, it shouldn’t matter if you use HTML 4 Strict, or XHTML 1.0 Strict, they are all incorporated into HTML5. I truly believe...
View ArticleBy: Jim Westergren
Oh, that’s well. HTML5 have quite many new elements which I think will be great for usability and perhaps even future SEO. Looking forward to it.
View ArticleBy: MWin
Hello Everyone, i read that article, and Emil does have some points… but i want to add something to the “leave the error-handling to the browsers” topic: One of the reasons why XHTML was introduced as...
View ArticleBy: MWin
One more thing… as for the looseness of html: consider following, simplified, code: Paragraph 1 Paragraph 2 Pargaraph 3 now, these 3 paragraphs, are they siblings to each other, or...
View ArticleBy: MWin
Hmm, didnt keep my html code snipped… try this: <body> <p> Pragraph 1 <p> Pragraph 2 <p> Pragraph 3 </body>
View ArticleBy: Web Design: What DOCTYPE do I use? « Obvious In Hindsight
[...] If you’d like to research an alternative opinion on why not to use XHTML, read here (Note: It’s an old article, much of it may not apply but interesting no less):...
View ArticleBy: Web Design: What is XHTML? « Obvious In Hindsight
[...] http://friendlybit.com/html/why-xhtml-is-a-bad-idea/ [...]
View ArticleBy: Steve Savage
After several years away from the web, I’ve decided to revitalize my site. I’d been debating providing both an XHTML (for application/xhtml+xml browsers) and HTML version (for text/html browsers). I’m...
View ArticleBy: K
This is an old blog post, but, boy am I glad I found it. Finally, someone who speaks clearly about this nonsense. I finally understand. Thank you, Emil. In hindsight, what should have happened in the...
View ArticleBy: Emil Stenström
@K: Thanks for your comment, and good to hear that I make sense in a world of information overload :) I truly think XHTML was one of the big reasons HTML5 has started to catch on now. People where...
View Article
