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."
"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.
- Google hardware history
16 May 2004
- Bush votes: inverse proportional to education and IQ
17 May 2004
- Related by category:
- How to create-react-app with Docker
17 November 2017
- Fastest way to find out if a file exists in S3 (with boto3)
16 June 2017
- How to throttle AND debounce an autocomplete input in React
01 March 2018
- Be very careful with your add_header in Nginx! You might make your site insecure
11 February 2018
- Displaying fetch() errors and unwanted responses in React
06 February 2019
- 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
- XHTML, HTML and CSS compressor
07 April 2004
- The importance of checking in Firefox
07 July 2008