<?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: Usability matters</title>
	<atom:link href="http://sellmic.com/blog/2007/02/20/usability-matters/feed/" rel="self" type="application/rss+xml" />
	<link>http://sellmic.com/blog/2007/02/20/usability-matters/</link>
	<description>Augusto's corner of art, code and fun</description>
	<lastBuildDate>Tue, 23 Feb 2010 08:25:54 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: b</title>
		<link>http://sellmic.com/blog/2007/02/20/usability-matters/comment-page-1/#comment-504</link>
		<dc:creator>b</dc:creator>
		<pubDate>Sat, 18 Aug 2007 20:57:46 +0000</pubDate>
		<guid isPermaLink="false">http://sellmic.com/blog/2007/02/20/usability-matters/#comment-504</guid>
		<description>I really like this design. You didn&#039;t cite where you got your definition of the typical user, but there are a lot of us who need more than just wget -r (or more likely, wget -np -r). When I run wget, I need to keep the manual page open in another window to keep track of all the switches, and this saves me that effort. It even covers a few of the things that are too well-hidden, like ignoring robots.txt (really, there are valid reasons to do so).

The author did a good job of avoiding the temptation to put every option in a dialog, which you&#039;ll see by checking the wget man page. I think the ones chosen are the sensible and common options that a user would want beyond -np -r, while the more obscure ones are omitted. In fact, one of my favorite switches, to identify as Googlebot, is missing.

The layout generally makes sense to me, but then, I&#039;ve used wget before, so I&#039;m not interested in ease of _initial_ use, but in ease of use. It&#039;s not pretty or inviting, but I think it solves its need admirably.</description>
		<content:encoded><![CDATA[<p>I really like this design. You didn&#8217;t cite where you got your definition of the typical user, but there are a lot of us who need more than just wget -r (or more likely, wget -np -r). When I run wget, I need to keep the manual page open in another window to keep track of all the switches, and this saves me that effort. It even covers a few of the things that are too well-hidden, like ignoring robots.txt (really, there are valid reasons to do so).</p>
<p>The author did a good job of avoiding the temptation to put every option in a dialog, which you&#8217;ll see by checking the wget man page. I think the ones chosen are the sensible and common options that a user would want beyond -np -r, while the more obscure ones are omitted. In fact, one of my favorite switches, to identify as Googlebot, is missing.</p>
<p>The layout generally makes sense to me, but then, I&#8217;ve used wget before, so I&#8217;m not interested in ease of _initial_ use, but in ease of use. It&#8217;s not pretty or inviting, but I think it solves its need admirably.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
