<?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: Should I use HTML 5 &#8211; Yes or No?	</title>
	<atom:link href="https://www.alananna.co.uk/blog/2009/11/should-i-use-html-5-yes-or-no/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.alananna.co.uk/blog/2009/11/should-i-use-html-5-yes-or-no/</link>
	<description>Tales from a down-shifted family - Making the most of modest means in West Wales</description>
	<lastBuildDate>Tue, 01 Feb 2011 00:35:22 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Moth		</title>
		<link>https://www.alananna.co.uk/blog/2009/11/should-i-use-html-5-yes-or-no/#comment-20083</link>

		<dc:creator><![CDATA[Moth]]></dc:creator>
		<pubDate>Tue, 01 Feb 2011 00:35:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.alananna.co.uk/blog/?p=2931#comment-20083</guid>

					<description><![CDATA[Found this quite interesting.  I&#039;ve just started work on a project, an online game actually that probably won&#039;t be ready for public consumption for at least another year.  I&#039;ve decided to go down the route of HTML 5.0 mainly because it works wonderfully in Chrome (my browser of choice) and the benefits and ease of coding were too much to resist.

Personally I think that Chrome&#039;s going to be a big player in the future but I can understand the worry when half the world is still trudging along using Internet Explorer.  I used to be an IE fan but I&#039;ve seen what Chrome can do and how much faster it is than both IE and Firefox.

Will I be burned for jumping the gun or will I reap the benefits of getting into HTML 5.0 in good time - who knows.  To be honest the project can succeed or fail, it&#039;s not my main income but I am very much enjoying using the features that HTML 5.0 and CSS 3.0 have brought so the sooner the rest of the world catch up the better.  

I also think that WebGL is going to change the face of the webscape too.  Some of the shining examples of user interfaces I&#039;ve seen are simply mind blowing, however, I was a little nervous at taking that final step as it requires a whole new skill set, although to be fair I&#039;ve done a fair amount of dabbling with OpenGL and Wii homebrew.  It would have been interesting but perhaps more than we need.]]></description>
			<content:encoded><![CDATA[<p>Found this quite interesting.  I&#8217;ve just started work on a project, an online game actually that probably won&#8217;t be ready for public consumption for at least another year.  I&#8217;ve decided to go down the route of HTML 5.0 mainly because it works wonderfully in Chrome (my browser of choice) and the benefits and ease of coding were too much to resist.</p>
<p>Personally I think that Chrome&#8217;s going to be a big player in the future but I can understand the worry when half the world is still trudging along using Internet Explorer.  I used to be an IE fan but I&#8217;ve seen what Chrome can do and how much faster it is than both IE and Firefox.</p>
<p>Will I be burned for jumping the gun or will I reap the benefits of getting into HTML 5.0 in good time &#8211; who knows.  To be honest the project can succeed or fail, it&#8217;s not my main income but I am very much enjoying using the features that HTML 5.0 and CSS 3.0 have brought so the sooner the rest of the world catch up the better.  </p>
<p>I also think that WebGL is going to change the face of the webscape too.  Some of the shining examples of user interfaces I&#8217;ve seen are simply mind blowing, however, I was a little nervous at taking that final step as it requires a whole new skill set, although to be fair I&#8217;ve done a fair amount of dabbling with OpenGL and Wii homebrew.  It would have been interesting but perhaps more than we need.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Alan		</title>
		<link>https://www.alananna.co.uk/blog/2009/11/should-i-use-html-5-yes-or-no/#comment-17640</link>

		<dc:creator><![CDATA[Alan]]></dc:creator>
		<pubDate>Thu, 05 Nov 2009 08:13:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.alananna.co.uk/blog/?p=2931#comment-17640</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.alananna.co.uk/blog/2009/11/should-i-use-html-5-yes-or-no/#comment-17636&quot;&gt;Andrew&lt;/a&gt;.

Thanks Andrew, you&#039;re probably right. I was thinking that my &#039;normal&#039; XHTML mark-up would be perfectly valid HTML 5 so the main changes would be to the doctype and tags within the head of each document. In essence very little would change except that I&#039;d be stating it was HTML 5 rather than XHTML... Of course that may be more than enough to confuse come browsers (no names mentioned!)

You&#039;re right about not using a Javascript trick to bring IE into line so it probably isn&#039;t a good idea to use the new semantic elements such as &lt;header&gt; until all of the major browsers support them properly. I&#039;ll stick with my normal &lt;div id=&quot;header&quot;&gt; for now. Which then leaves the question of &#039;what&#039;s the point of using HTML 5&#039; for this project if I&#039;m not going to be using any of the new features? Probably none except that it keeps me ahead of the curve and I get to use the perfectly sucinct &lt; !DOCTYPE html&gt;

I guess it won&#039;t be too much trouble to test it as HTML5 and see if there are any problems. If there are then it shouldn&#039;t be too difficult to revert back to XHTML.

Thanks for the heads up on the comment box too... It didn&#039;t happen for me unless I zoomed in, which is probably why I never noticed but it&#039;s all fixed now. (hopefully).

Al.&lt;/div&gt;&lt;/header&gt;]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.alananna.co.uk/blog/2009/11/should-i-use-html-5-yes-or-no/#comment-17636">Andrew</a>.</p>
<p>Thanks Andrew, you&#8217;re probably right. I was thinking that my &#8216;normal&#8217; XHTML mark-up would be perfectly valid HTML 5 so the main changes would be to the doctype and tags within the head of each document. In essence very little would change except that I&#8217;d be stating it was HTML 5 rather than XHTML&#8230; Of course that may be more than enough to confuse come browsers (no names mentioned!)</p>
<p>You&#8217;re right about not using a Javascript trick to bring IE into line so it probably isn&#8217;t a good idea to use the new semantic elements such as </p>
<header> until all of the major browsers support them properly. I&#8217;ll stick with my normal </p>
<div id="header"> for now. Which then leaves the question of &#8216;what&#8217;s the point of using HTML 5&#8217; for this project if I&#8217;m not going to be using any of the new features? Probably none except that it keeps me ahead of the curve and I get to use the perfectly sucinct < !DOCTYPE html></p>
<p>I guess it won&#8217;t be too much trouble to test it as HTML5 and see if there are any problems. If there are then it shouldn&#8217;t be too difficult to revert back to XHTML.</p>
<p>Thanks for the heads up on the comment box too&#8230; It didn&#8217;t happen for me unless I zoomed in, which is probably why I never noticed but it&#8217;s all fixed now. (hopefully).</p>
<p>Al.</p></div>
</header>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Andrew		</title>
		<link>https://www.alananna.co.uk/blog/2009/11/should-i-use-html-5-yes-or-no/#comment-17636</link>

		<dc:creator><![CDATA[Andrew]]></dc:creator>
		<pubDate>Wed, 04 Nov 2009 12:08:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.alananna.co.uk/blog/?p=2931#comment-17636</guid>

					<description><![CDATA[I&#039;d say no. Until HTML5 is supported by final versions of the major browsers you&#039;re only making work for yourself. Relying on javascript trickery to make things work is a bad idea. Being aware of the specs and knowing how to use the new elements etc. would be sufficient I&#039;d have thought, but I&#039;d be glad to be proved wrong.

BTW, your comment box flows under the Categories list in FF on Windows, means I can&#039;t see the last 3 or 4 characters of any line.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;d say no. Until HTML5 is supported by final versions of the major browsers you&#8217;re only making work for yourself. Relying on javascript trickery to make things work is a bad idea. Being aware of the specs and knowing how to use the new elements etc. would be sufficient I&#8217;d have thought, but I&#8217;d be glad to be proved wrong.</p>
<p>BTW, your comment box flows under the Categories list in FF on Windows, means I can&#8217;t see the last 3 or 4 characters of any line.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
