<?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: IE Team Meddles in HTML5</title>
	<atom:link href="http://darylteo.com/blog/2009/08/11/ie-team-meddles-in-html5/feed/" rel="self" type="application/rss+xml" />
	<link>http://darylteo.com/blog/2009/08/11/ie-team-meddles-in-html5/</link>
	<description>Bits and blobs on anything tech</description>
	<lastBuildDate>Sat, 31 Dec 2011 19:51:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sam</title>
		<link>http://darylteo.com/blog/2009/08/11/ie-team-meddles-in-html5/comment-page-1/#comment-11810</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Sat, 15 Aug 2009 05:43:52 +0000</pubDate>
		<guid isPermaLink="false">http://darylteo.com/blog/2009/08/11/ie-team-meddles-in-html5/#comment-11810</guid>
		<description>I think everyone else has enough clout now not to let Microsoft derail HTML5. And I don&#039;t think Microsoft are going to drop out or suspend browser development in the near future, given its renewed push into the web world. It is only a good thing that they&#039;re there, rather than not. Abandoning IE8 solves nothing really - like you said, these initiatives are fluid anyway; you will still likely have to do browser-dependent implementations. (IE6 on the other hand should really be put to sleep - I&#039;m tempted to feed it the dumbed-down mobile version on my next site.)

I hope they get HTML5 sorted out properly, without the huge holes in it that ODF had allowing Microsoft to &#039;drive a truck through it and break everything&#039;. (Arguably, the only other reasonable choice they had for ODF was to not implement it for Excel.)

That said, it would be nice if we didn&#039;t have to wait til 2022 for that - http://www.webmonkey.com/blog/HTML_5_Won_t_Be_Ready_Until_2022DOT_Yes__2022DOT

HTML already mostly follows the lead provided by Flash and it&#039;ll only be further behind in the future with Silverlight/JavaFX and Google Gears/NC. I personally wish browsers would be more innovative and experiment more in the HTML arena - Safari was good start.</description>
		<content:encoded><![CDATA[<p>I think everyone else has enough clout now not to let Microsoft derail HTML5. And I don&#8217;t think Microsoft are going to drop out or suspend browser development in the near future, given its renewed push into the web world. It is only a good thing that they&#8217;re there, rather than not. Abandoning IE8 solves nothing really &#8211; like you said, these initiatives are fluid anyway; you will still likely have to do browser-dependent implementations. (IE6 on the other hand should really be put to sleep &#8211; I&#8217;m tempted to feed it the dumbed-down mobile version on my next site.)</p>
<p>I hope they get HTML5 sorted out properly, without the huge holes in it that ODF had allowing Microsoft to &#8216;drive a truck through it and break everything&#8217;. (Arguably, the only other reasonable choice they had for ODF was to not implement it for Excel.)</p>
<p>That said, it would be nice if we didn&#8217;t have to wait til 2022 for that &#8211; <a href="http://www.webmonkey.com/blog/HTML_5_Won_t_Be_Ready_Until_2022DOT_Yes__2022DOT" rel="nofollow">http://www.webmonkey.com/blog/HTML_5_Won_t_Be_Ready_Until_2022DOT_Yes__2022DOT</a></p>
<p>HTML already mostly follows the lead provided by Flash and it&#8217;ll only be further behind in the future with Silverlight/JavaFX and Google Gears/NC. I personally wish browsers would be more innovative and experiment more in the HTML arena &#8211; Safari was good start.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

