Most administrators are lazy. If you write software for thousands or millions of users, sane defaults are a must. I find it useful to keep Saint-Exupéry in mind: <i>&quot;It seems that perfection is attained not when there is nothing more to add, but when there is nothing more to remove.&quot;</i><p>Let&#x27;s look at the first lines of WordPress&#x27;s default template:<p><pre><code>  &lt;!DOCTYPE html&gt;
  &lt;html xmlns=&quot;http:&#x2F;&#x2F;www.w3.org&#x2F;1999&#x2F;xhtml&quot; dir=&quot;ltr&quot; lang=&quot;en-US&quot;&gt;
  &lt;head profile=&quot;http:&#x2F;&#x2F;gmpg.org&#x2F;xfn&#x2F;11&quot;&gt;
</code></pre>
Why bother with <i>xmlns</i> if it&#x27;s not well-formed XML anyway?<p>Why <i>dir</i> and <i>lang</i> if you don&#x27;t really know what language the content is in? We now have the funny situation that most non-English pages wrongly declare <i>lang=&quot;en-US&quot;</i> because W3C evangelists told template authors that <i>lang</i> is really important, rendering the attribute completely useless.<p>What the <i>heck</i> is <i>profile=&quot;<a href="http:&#x2F;&#x2F;gmpg.org&#x2F;xfn&#x2F;11&quot;" rel="nofollow">http:&#x2F;&#x2F;gmpg.org&#x2F;xfn&#x2F;11&quot;</a> </i> supposed to do?