<?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: Fast Prototyping WoT Apps with NIWEA</title>
	<atom:link href="http://www.webofthings.org/2010/06/29/fast-prototyping-wot-apps-with-niwea/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webofthings.org/2010/06/29/fast-prototyping-wot-apps-with-niwea/</link>
	<description>Architecting the Web of Things, for techies and thinkers!</description>
	<lastBuildDate>Thu, 09 Feb 2012 12:08: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: Rick Bullotta</title>
		<link>http://www.webofthings.org/2010/06/29/fast-prototyping-wot-apps-with-niwea/comment-page-1/#comment-5519</link>
		<dc:creator>Rick Bullotta</dc:creator>
		<pubDate>Tue, 29 Jun 2010 16:28:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.webofthings.com/2010/06/29/fast-prototyping-wot-apps-with-niwea/#comment-5519</guid>
		<description>NIWEA is part of the equation (we&#039;re aggressively moving in this direction for our runtime application UI), but consumption of services/data needs to become cleaner/easier/more consistent, and offline application storage needs to be more unified (HTML5 certainly is a start).

The other important consideration that is being overlooked is the effort by many browser makers to exploit hardware acceleration and script JIT-ing/compilation to enable HTML-centric apps to approach native speeds.  This is a HUGE enabler for the NIWEA vision.  I have to give Microsoft some big props for what they&#039;re doing in IE9 as well as what Google as done with Chrome. 

The future looks bright!</description>
		<content:encoded><![CDATA[<p>NIWEA is part of the equation (we&#8217;re aggressively moving in this direction for our runtime application UI), but consumption of services/data needs to become cleaner/easier/more consistent, and offline application storage needs to be more unified (HTML5 certainly is a start).</p>
<p>The other important consideration that is being overlooked is the effort by many browser makers to exploit hardware acceleration and script JIT-ing/compilation to enable HTML-centric apps to approach native speeds.  This is a HUGE enabler for the NIWEA vision.  I have to give Microsoft some big props for what they&#8217;re doing in IE9 as well as what Google as done with Chrome. </p>
<p>The future looks bright!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

