<?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: The future of the web</title>
	<atom:link href="http://agoln.net/archives/12/feed" rel="self" type="application/rss+xml" />
	<link>http://agoln.net/archives/12</link>
	<description>Development and personal site</description>
	<lastBuildDate>Wed, 12 May 2010 16:55:16 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Bennett Andrews</title>
		<link>http://agoln.net/archives/12/comment-page-1#comment-4</link>
		<dc:creator>Bennett Andrews</dc:creator>
		<pubDate>Mon, 23 Apr 2007 00:15:53 +0000</pubDate>
		<guid isPermaLink="false">http://agoln.net/archives/12#comment-4</guid>
		<description>Plus who wants to hack on a thin client?  It&#039;s just another way to take the fun out of computing... LAME</description>
		<content:encoded><![CDATA[<p>Plus who wants to hack on a thin client?  It&#8217;s just another way to take the fun out of computing&#8230; LAME</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke Hoersten</title>
		<link>http://agoln.net/archives/12/comment-page-1#comment-3</link>
		<dc:creator>Luke Hoersten</dc:creator>
		<pubDate>Fri, 20 Apr 2007 21:03:45 +0000</pubDate>
		<guid isPermaLink="false">http://agoln.net/archives/12#comment-3</guid>
		<description>Another reason, to support your article, that computers wont go to thin clients is because, no matter how fast the internet gets, local hardware will &lt;em&gt;always&lt;/em&gt; be faster. I think in the late &#039;80s people thought thin clients were the wave of the future as well. That&#039;s why Purdue has all those old sunblade thin clients. Also notice we don&#039;t use them anymore. They are completely unusable. Also, look in the new CS computer labs. The new labs have the most expensive workstations you can get.

The reason for this: the internet is scaled in proportion to hardware. And like I said before, hardware will always be faster locally and software is going to continue to require more resources. Some apps &lt;em&gt;will&lt;/em&gt; be migrated to the internet (like office applications are right now) but, they are the oldest apps we have! The office apps were some of the first apps made for Windows so it only makes sense that they would be the first to go. It&#039;s hard to see what the big new apps are now, but, the apps moving to the internet &lt;em&gt;are&lt;/em&gt; being replaced.

I realize you said some of this in your post, I just wanted to put a different spin on it.</description>
		<content:encoded><![CDATA[<p>Another reason, to support your article, that computers wont go to thin clients is because, no matter how fast the internet gets, local hardware will <em>always</em> be faster. I think in the late &#8217;80s people thought thin clients were the wave of the future as well. That&#8217;s why Purdue has all those old sunblade thin clients. Also notice we don&#8217;t use them anymore. They are completely unusable. Also, look in the new CS computer labs. The new labs have the most expensive workstations you can get.</p>
<p>The reason for this: the internet is scaled in proportion to hardware. And like I said before, hardware will always be faster locally and software is going to continue to require more resources. Some apps <em>will</em> be migrated to the internet (like office applications are right now) but, they are the oldest apps we have! The office apps were some of the first apps made for Windows so it only makes sense that they would be the first to go. It&#8217;s hard to see what the big new apps are now, but, the apps moving to the internet <em>are</em> being replaced.</p>
<p>I realize you said some of this in your post, I just wanted to put a different spin on it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.320 seconds -->
