<?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: IE8 Meta Declaration Not Required For HTML5</title>
	<atom:link href="http://ifacethoughts.net/2008/01/24/ie8-meta-declaration-not-required-for-html5/feed/" rel="self" type="application/rss+xml" />
	<link>http://ifacethoughts.net/2008/01/24/ie8-meta-declaration-not-required-for-html5/</link>
	<description>Thoughts on software development and related, by Abhijit Nadgouda</description>
	<lastBuildDate>Mon, 08 Mar 2010 04:15:50 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeremy</title>
		<link>http://ifacethoughts.net/2008/01/24/ie8-meta-declaration-not-required-for-html5/comment-page-1/#comment-353707</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Thu, 11 Dec 2008 19:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2008/01/24/ie8-meta-declaration-not-required-for-html5/#comment-353707</guid>
		<description>I don&#039;t think it matters much. The meta tag is just for you to help make sure your old, crappy, non-standards-compliant code will keep working like it was tested, even though you&#039;re not going to update it.

For future development, develop to standards! Not to any specific browser version.

If you have to support browsers that don&#039;t support standards, nothing has changed. You still have to add your fixes and hacks sometimes, but keep them seperated (e.g., external CSS files and JavaScript files that are linked/included) so it&#039;s easy to take them aways as old browsers die.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think it matters much. The meta tag is just for you to help make sure your old, crappy, non-standards-compliant code will keep working like it was tested, even though you&#8217;re not going to update it.</p>
<p>For future development, develop to standards! Not to any specific browser version.</p>
<p>If you have to support browsers that don&#8217;t support standards, nothing has changed. You still have to add your fixes and hacks sometimes, but keep them seperated (e.g., external CSS files and JavaScript files that are linked/included) so it&#8217;s easy to take them aways as old browsers die.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
