<?xml version="1.0" encoding="UTF-8"?>
<essay xml:lang="en" version="5.0" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:gal="http://norman.walsh.name/rdf/gallery#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
<info>
    
    
    
    
    
    
    
    
    
    
    
    
<title>In praise of web 1.0</title><biblioid class="uri">http://norman.walsh.name/2006/04/03/web10</biblioid>
<volumenum>9</volumenum>
<issuenum>37</issuenum>
<pubdate>2006-04-03T17:38:47-04:00</pubdate>
<date>$Date: 2006-04-03 19:16:25 -0400 (Mon, 03 Apr 2006) $</date>
<author>
      <personname>
<firstname>Norman</firstname>
	<surname>Walsh</surname>
</personname>
    </author>
<copyright>
      <year>2006</year>
      <holder>Norman Walsh</holder>
    </copyright>
<abstract>
<para>I'm as excited as the next web developer about the whiz-bang,
AJAX, JavaScript magic of web 2.0 interfaces, but let's not forget
that there's still value in designing workable interfaces for less
powerful browsers.</para>
</abstract>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#Email"/>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#Gadgets"/>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#RSS"/>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#TheWeb"/>
</info>

<para xml:id="p1">A while back, I discovered the convenience of forwarding
all my personal mail to my
<link xlink:href="http://en.wikipedia.org/wiki/Gmail">GMail</link>
account. It's not my primary interface for reading mail, that's now and
forever going to be
<link xlink:href="http://en.wikipedia.org/wiki/Emacs">Emacs</link> on my 
laptop, but it's handy to be able to get mail, or lookup mail, when I'm
waiting in an airport or bored in the supermarket check-out line.</para>

<para xml:id="p2">The key feature of GMail for me is that it works on my
<link xlink:href="http://en.wikipedia.org/wiki/T-Mobile_Sidekick">Sidekick</link>
which has some
<link xlink:href="http://en.wikipedia.org/wiki/JavaScript">JavaScript</link>
capability, but nothing like what's needed to support
a full web 2.0 interface.
The beta version of
<link xlink:href="http://en.wikipedia.org/wiki/Yahoo%21">Yahoo!</link>’s mail
client is fancy and whiz-bang, but doesn't work at all on my Sidekick so
I very quickly gave up on it. (I'm also not a big fan of the three-panel
mail reader paradigm, but that's not relevant here.)</para>

<para xml:id="p3">Similarly, I occasionally fiddle with possible replacements for
<link xlink:href="http://en.wikipedia.org/wiki/Bloglines">Bloglines</link>
which doesn't seem to be getting much maintenance these days. As with mail,
the fact that I can read Bloglines on my Sidekick is critical: it's an even
more appealing way to spend idle time in a check-out line.
Most recently,
<link xlink:href="http://www.feedlounge.com/">FeedLounge</link> showed
promise until it turned out to be completely unusable in the less-capable
browser that my Sidekick sports.</para>

<para xml:id="p4">If you want to sell me a service that I'm going to really use
(that is, rely on and use exclusive of your competition), don't forget
to make it <emphasis>usable</emphasis> in web 1.0, without all the
bells and whistles.
</para>

</essay>

