<?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: Web 3.0</title>
	<atom:link href="http://www.benjamintseng.com/2009/11/web-30/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.benjamintseng.com/2009/11/web-30/</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 16:03:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Platform perils</title>
		<link>http://www.benjamintseng.com/2009/11/web-30/comment-page-1/#comment-344</link>
		<dc:creator>Platform perils</dc:creator>
		<pubDate>Mon, 31 May 2010 13:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.benjamintseng.com/2009/11/web-3-0/#comment-344</guid>
		<description>[...] of the most impressive developments in the web and the mobile phone space has been the emergence of new platforms for software developers to [...]</description>
		<content:encoded><![CDATA[<p>[...] of the most impressive developments in the web and the mobile phone space has been the emergence of new platforms for software developers to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What it will take to get me to switch to Chrome</title>
		<link>http://www.benjamintseng.com/2009/11/web-30/comment-page-1/#comment-265</link>
		<dc:creator>What it will take to get me to switch to Chrome</dc:creator>
		<pubDate>Fri, 08 Jan 2010 15:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.benjamintseng.com/2009/11/web-3-0/#comment-265</guid>
		<description>[...] Advanced web standard support – I think its pretty odd that despite being a major proponent of the HTML5 standard and new rich browser technologies like WebGL and Native Client, that Chrome has yet to truly distance itself from its browser peers in terms of support for these new standards. True, the technologies themselves are still under development and very few websites exist which support them, but a differentiated level of support for these new technologies would give me a whole set of reasons to pick Chrome over its browser peers, especially given the direction I expect the rich web to move. [...]</description>
		<content:encoded><![CDATA[<p>[...] Advanced web standard support – I think its pretty odd that despite being a major proponent of the HTML5 standard and new rich browser technologies like WebGL and Native Client, that Chrome has yet to truly distance itself from its browser peers in terms of support for these new standards. True, the technologies themselves are still under development and very few websites exist which support them, but a differentiated level of support for these new technologies would give me a whole set of reasons to pick Chrome over its browser peers, especially given the direction I expect the rich web to move. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

