<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 10 Reasons Why HTML 5 Will Change The Web (And 1 Why It Won&#8217;t)</title>
	<atom:link href="http://www.techielife.com/10-reasons-why-html-5-will-change-the-web-and-1-why-it-wont/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techielife.com/10-reasons-why-html-5-will-change-the-web-and-1-why-it-wont/</link>
	<description>Food, Shelter, Clothing ... and now, Technology!</description>
	<lastBuildDate>Wed, 17 Aug 2011 18:10:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: JIRA: Moodle</title>
		<link>http://www.techielife.com/10-reasons-why-html-5-will-change-the-web-and-1-why-it-wont/comment-page-1/#comment-1446</link>
		<dc:creator>JIRA: Moodle</dc:creator>
		<pubDate>Mon, 13 Jul 2009 12:13:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.techielife.com/?p=37#comment-1446</guid>
		<description>&lt;strong&gt;[MDL-825] javascript focus is annoying / disruptive...&lt;/strong&gt;

Just to jot this down for now, HTML5 appears to have taken this into account: 

9. Allow users to disable autofocus: How many times have you started filling a form while the page was loading, only to be rudely forced onto another field after the pag....</description>
		<content:encoded><![CDATA[<p><strong>[MDL-825] javascript focus is annoying / disruptive&#8230;</strong></p>
<p>Just to jot this down for now, HTML5 appears to have taken this into account: </p>
<p>9. Allow users to disable autofocus: How many times have you started filling a form while the page was loading, only to be rudely forced onto another field after the pag&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pligg.com</title>
		<link>http://www.techielife.com/10-reasons-why-html-5-will-change-the-web-and-1-why-it-wont/comment-page-1/#comment-443</link>
		<dc:creator>pligg.com</dc:creator>
		<pubDate>Wed, 31 Dec 2008 07:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.techielife.com/?p=37#comment-443</guid>
		<description>&lt;strong&gt;10 Reasons Why HTML 5 Will Change The Web...&lt;/strong&gt;

HTML5 is currently in the draft stage, and the latest specification is available at the W3C web site. Listed a 10 reasons why it will change the web and 1 why it won&#039;t...</description>
		<content:encoded><![CDATA[<p><strong>10 Reasons Why HTML 5 Will Change The Web&#8230;</strong></p>
<p>HTML5 is currently in the draft stage, and the latest specification is available at the W3C web site. Listed a 10 reasons why it will change the web and 1 why it won&#8217;t&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SneakyWho_am_i</title>
		<link>http://www.techielife.com/10-reasons-why-html-5-will-change-the-web-and-1-why-it-wont/comment-page-1/#comment-93</link>
		<dc:creator>SneakyWho_am_i</dc:creator>
		<pubDate>Wed, 08 Oct 2008 09:08:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.techielife.com/?p=37#comment-93</guid>
		<description>Great post, I&#039;m excited about some of these features too, although yes, Ian already pointed out the good news (not that I know him, not that he knows me, not that I&#039;m important in any way) and that is:

HTML5 now is ready as soon as you feel brave enough to use it.

2022 is the date when browsers will be ready, not the date when the specification was ready.

For comparison, there exists no 100% compliant implementation of HTML4.01 or any flavour of XHTML to this very day, even though the relevant specifications were penned last century.</description>
		<content:encoded><![CDATA[<p>Great post, I&#8217;m excited about some of these features too, although yes, Ian already pointed out the good news (not that I know him, not that he knows me, not that I&#8217;m important in any way) and that is:</p>
<p>HTML5 now is ready as soon as you feel brave enough to use it.</p>
<p>2022 is the date when browsers will be ready, not the date when the specification was ready.</p>
<p>For comparison, there exists no 100% compliant implementation of HTML4.01 or any flavour of XHTML to this very day, even though the relevant specifications were penned last century.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Hickson</title>
		<link>http://www.techielife.com/10-reasons-why-html-5-will-change-the-web-and-1-why-it-wont/comment-page-1/#comment-34</link>
		<dc:creator>Ian Hickson</dc:creator>
		<pubDate>Sun, 21 Sep 2008 03:45:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.techielife.com/?p=37#comment-34</guid>
		<description>It&#039;ll be ready long before 2022. The 2022 date is the date we expect to have two complete _bug-free_ implementations of the whole of HTML5. We _still_ haven&#039;t reached that point with any previous version of HTML or the DOM or JS, so by the logic that makes 2022 a problem, the whole Web isn&#039;t ready yet. :-)

You can actually use many parts of HTML5 today in various browsers, with more stuff being implemented every week.</description>
		<content:encoded><![CDATA[<p>It&#8217;ll be ready long before 2022. The 2022 date is the date we expect to have two complete _bug-free_ implementations of the whole of HTML5. We _still_ haven&#8217;t reached that point with any previous version of HTML or the DOM or JS, so by the logic that makes 2022 a problem, the whole Web isn&#8217;t ready yet. <img src='http://www.techielife.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>You can actually use many parts of HTML5 today in various browsers, with more stuff being implemented every week.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

