<?xml version="1.0" encoding="UTF-8"?><item><title>An advantage of web apps</title><description>I've got Microsoft MapPoint installed on my system, but it's faster for&#13;
me to get a map for a given location using Google Maps.&amp;nbsp; I've got&#13;
a Desktop Search tool installed, but it's faster to find something on&#13;
the Internet (searching billions of pages) than it is to find something&#13;
on my own computer.&lt;br&gt;&#13;
&lt;br&gt;&#13;
This is because of application launch time, and paging.&amp;nbsp; If I've&#13;
been busy on my computer, it has to do a lot of swapping to bring up a&#13;
new application (and I've got a gig of RAM).&amp;nbsp; When I want a map,&#13;
the only software my computer needs to run is a browser.&amp;nbsp; The time&#13;
it takes to download the map is less than the time it takes to launch&#13;
MapPoint.&lt;br&gt;&#13;
&lt;br&gt;&#13;
The same is true in almost every instance.&lt;br&gt;&#13;
&lt;br&gt;&#13;
Remote Desktop makes it possible to use a remote "rich client"&#13;
application on my local system.&amp;nbsp; With a little tweaking to make&#13;
the remote application seem more like a window on my desktop than a&#13;
complete remote desktop (more like X Windows), you could run almost any&#13;
application remotely faster than you could run it locally, simply&#13;
because the hardware that's running that application is dedicated to it.&lt;br&gt;&#13;
&lt;br&gt;&#13;
This seems like a more promising future than the current AJAX fad and&#13;
trying to pretend the browser is a rich client.&amp;nbsp; Browsers still&#13;
have some serious drawbacks when it comes to creating applications.&lt;br&gt;&#13;
&lt;br&gt;&#13;
And for the rich vs reach argument; having a rich client application&#13;
running remotely means I could also install the rich client application&#13;
locally and take it with me (assuming it's not something that needs&#13;
data from the remote hardware it's running on).&lt;br&gt;&#13;
&lt;br&gt;&#13;
One of the compelling things about ZIM is that it had a thin client&#13;
runtime that would remote the GUI using very high level constructs&#13;
(like "put this button here and tell me when the user clicks&#13;
it").&amp;nbsp; The admin could run the app server on the local box, or on&#13;
a remote box, and the user didn't need to know the difference.&lt;br&gt;&#13;
&lt;br&gt;&#13;
There's still no really rich client tier for a 3 tier or n tier&#13;
architecture, as far as I can tell (admittedly I haven't searched&#13;
extensively). &lt;br&gt;&#13;
&lt;br&gt;</description><pubDate>Thu, 01 Sep 2005 19:17:09 GMT</pubDate></item>