<feed xmlns="http://www.w3.org/2005/Atom" xmlns:foaf="http://xmlns.com/foaf/0.1/"><title>norman.walsh.name: Comments on /2008/01/22/html5</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/01/22/html5"/><id>http://norman.walsh.name/2008/01/22/html5/comments.atom</id><updated>2012-02-13T06:19:03.75973Z</updated><entry><title>Comment 1 on /2008/01/22/html5</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/01/22/html5#comment0001"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0001</id><published>2008-05-01T17:37:13Z</published><updated>2008-05-01T17:37:13Z</updated><author><name>Rob</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Few will dispute that HTML5 will be adopted very differently than HTML. HTML was adopted by everyone at the same time because the W3 was the next big thing, browsers were crude and at first they all introduced their own "extensions". People (by which I mean me) authored HTML without even knowing what a doctype declaration was, and books that TAUGHT "web design" ignroed closing tags and semantics. That led people to author invalid documents in ignorance.
</p>
    <p>
When W3C recomends their next version of (x)HTML, regardless whether well-formed, valid XML is required, the early adopters will be the highly technical people who author compliant XML by habit. The plebs will probably never learn the intricacies of HTML5. For them, HTML4 is good enough, and besides that the trend has been for sites to provide their own bracket-based markup, along the lines of wiki markup or bbcode.
</p>
    <p>
So I wouldn't worry about messy HTML5 polluting the web... even if it is technically allowed I don't think many will use it.</p>
  </div></content></entry></feed>

