This blog post is
14 years old! Most likely, its content is outdated.
Especially if it's technical.
This site does not use XHTML although it will some time in the future. The next version of the IssueTrackerProduct will. I've never really understood why one should use XHTML but this site gives the answer:
"What's in it for me?
In the short term, probably not a lot, but the Web is moving very quickly and you always have to think ahead.
If using XHTML only helps to tighten-up your markup, getting rid of ambiguities and sloppy coding, then it's already improving the robustness of your pages across browsers."
and
"The use of valid XHTML helps to guarantee that any pages you build now will work well into the foreseeable future in all current and future browsers."
Good. Now I know.
- Previous:
- Google hardware history
16 May 2004
- Next:
- Bush votes: inverse proportional to education and IQ
17 May 2004
- Related by Keyword:
- How much HTML is too much for optimal web performance
17 October 2018
- HTML whitespace "compression" - don't bother!
11 March 2013
- How to use premailer as a command line script
13 July 2012
- The importance of checking in Firefox
07 July 2008
- XHTML Transitional versus Strict
05 November 2004
- Related by Text:
- jQuery and Highslide JS
08 January 2008
- I'm back! Peterbe.com has been renewed
05 June 2005
- Anti-McCain propaganda videos
12 August 2008
- Ever wondered how much $87 Billion is?
04 November 2003
- Guake, not Yakuake or Yeahconsole
23 January 2010
