<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Web 3.0</title>
	<link>http://wealthfly.com/blog/2007/10/03/web-30/</link>
	<description>A blog for investment advisors, brokers and financial planners.</description>
	<pubDate>Tue, 06 Jan 2009 09:32:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: WealthFly &#187; Google Chrome</title>
		<link>http://wealthfly.com/blog/2007/10/03/web-30/#comment-5941</link>
		<dc:creator>WealthFly &#187; Google Chrome</dc:creator>
		<pubDate>Tue, 02 Sep 2008 16:19:57 +0000</pubDate>
		<guid>http://wealthfly.com/blog/2007/10/03/web-30/#comment-5941</guid>
		<description>[...] book. Browsers are unstable, too slow, not secure, and inherently single-threaded. Most of the new Rich Internet Application (RIA) technologies use plug-ins designed specifically to bypass these limitations. For example, Microsoft [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] book. Browsers are unstable, too slow, not secure, and inherently single-threaded. Most of the new Rich Internet Application (RIA) technologies use plug-ins designed specifically to bypass these limitations. For example, Microsoft [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WealthFly &#187; A Night At the Opera</title>
		<link>http://wealthfly.com/blog/2007/10/03/web-30/#comment-502</link>
		<dc:creator>WealthFly &#187; A Night At the Opera</dc:creator>
		<pubDate>Wed, 28 Nov 2007 16:21:58 +0000</pubDate>
		<guid>http://wealthfly.com/blog/2007/10/03/web-30/#comment-502</guid>
		<description>[...] Nice to know I&#8217;m not going crazy. Other people think the recent problems stem from all the new Web 2.0 stuff we&#8217;re using. These observations reinforce my belief that Microsoft Silverlight will be the Next Big Thing and all these Web 2.0 developers will soon be building Silverlight apps. But that&#8217;s not what this post is about. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Nice to know I&#8217;m not going crazy. Other people think the recent problems stem from all the new Web 2.0 stuff we&#8217;re using. These observations reinforce my belief that Microsoft Silverlight will be the Next Big Thing and all these Web 2.0 developers will soon be building Silverlight apps. But that&#8217;s not what this post is about. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amnon</title>
		<link>http://wealthfly.com/blog/2007/10/03/web-30/#comment-441</link>
		<dc:creator>Amnon</dc:creator>
		<pubDate>Sun, 11 Nov 2007 19:32:05 +0000</pubDate>
		<guid>http://wealthfly.com/blog/2007/10/03/web-30/#comment-441</guid>
		<description>I also recommend checking out JNEXT ( &lt;a href="http://jnext.org" rel="nofollow"&gt;http://jnext.org&lt;/a&gt; ) which enables you to delegate from JavaScript to native code any parts that are CPU intensive or simply unavailable for JavaScript</description>
		<content:encoded><![CDATA[<p>I also recommend checking out JNEXT ( <a href="http://jnext.org" rel="nofollow" onclick="javascript:pageTracker._trackPageview('/outbound/comment/http://jnext.org');">http://jnext.org</a> ) which enables you to delegate from JavaScript to native code any parts that are CPU intensive or simply unavailable for JavaScript</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Hammant</title>
		<link>http://wealthfly.com/blog/2007/10/03/web-30/#comment-413</link>
		<dc:creator>Paul Hammant</dc:creator>
		<pubDate>Mon, 22 Oct 2007 22:58:05 +0000</pubDate>
		<guid>http://wealthfly.com/blog/2007/10/03/web-30/#comment-413</guid>
		<description>Nice. Take a look at swiby:

http://swiby.codehaus.org

Its trying to be a worthy inheritor of web 3.0 title. Perhaps in the way that you suggest.</description>
		<content:encoded><![CDATA[<p>Nice. Take a look at swiby:</p>
<p><a href="http://swiby.codehaus.org" rel="nofollow" onclick="javascript:pageTracker._trackPageview('/outbound/comment/http://swiby.codehaus.org');">http://swiby.codehaus.org</a></p>
<p>Its trying to be a worthy inheritor of web 3.0 title. Perhaps in the way that you suggest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geof Harries</title>
		<link>http://wealthfly.com/blog/2007/10/03/web-30/#comment-392</link>
		<dc:creator>Geof Harries</dc:creator>
		<pubDate>Thu, 04 Oct 2007 13:19:25 +0000</pubDate>
		<guid>http://wealthfly.com/blog/2007/10/03/web-30/#comment-392</guid>
		<description>I think you're missing the point with AIR. It is not about running applications inside the browser. The runtime enables that same experience to operate outside of the browser, on the desktop. Being able to code in HTML/JS, Flex or Flash and create an app knocks down a big barrier to entry. That's a core strength of AIR.

Also, mobile-specific applications will not fade away; in fact, it's the opposite. Even if more mobile devices gain a "normal" web browser, the small screen demands a wholly different approach.

People use mobile devices much differently than a desktop computer. Sure, there's movies and ringtones, but most of the time, the information request is about here and now, as quickly as possible. Totally different mental model than the desktop experience.</description>
		<content:encoded><![CDATA[<p>I think you&#8217;re missing the point with AIR. It is not about running applications inside the browser. The runtime enables that same experience to operate outside of the browser, on the desktop. Being able to code in HTML/JS, Flex or Flash and create an app knocks down a big barrier to entry. That&#8217;s a core strength of AIR.</p>
<p>Also, mobile-specific applications will not fade away; in fact, it&#8217;s the opposite. Even if more mobile devices gain a &#8220;normal&#8221; web browser, the small screen demands a wholly different approach.</p>
<p>People use mobile devices much differently than a desktop computer. Sure, there&#8217;s movies and ringtones, but most of the time, the information request is about here and now, as quickly as possible. Totally different mental model than the desktop experience.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
