<?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: Reinventing the desktop (part 2): I heard you like lists&#8230; [text version]</title>
	<atom:link href="http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/feed/" rel="self" type="application/rss+xml" />
	<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/</link>
	<description></description>
	<lastBuildDate>Thu, 25 Mar 2010 06:32:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Candy Randy</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-4056</link>
		<dc:creator>Candy Randy</dc:creator>
		<pubDate>Thu, 08 Oct 2009 23:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-4056</guid>
		<description>&quot;You left out hot keys, and a quickly accessible app-launch.

alt+f2 and type application (my favorite launcher is katapult and the keys for that are alt+space)
and in general, hotkeys it up… win+w is web browser, win+f is file manager, win+e is text editor, and win+d is doom3 (always a pleasure to accidentally open it between the two and get side tracked for an hour :)&quot;

That is nowhere near as efficient and easy as it could be. There is a much better way, but I will reveal all soon...

I&#039;m just amazed nobody has thought of it already - it shows how unable to think outside the box the entire world of computer users is...</description>
		<content:encoded><![CDATA[<p>&#8220;You left out hot keys, and a quickly accessible app-launch.</p>
<p>alt+f2 and type application (my favorite launcher is katapult and the keys for that are alt+space)<br />
and in general, hotkeys it up… win+w is web browser, win+f is file manager, win+e is text editor, and win+d is doom3 (always a pleasure to accidentally open it between the two and get side tracked for an hour :)&#8221;</p>
<p>That is nowhere near as efficient and easy as it could be. There is a much better way, but I will reveal all soon&#8230;</p>
<p>I&#8217;m just amazed nobody has thought of it already &#8211; it shows how unable to think outside the box the entire world of computer users is&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Candy Randy</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-4055</link>
		<dc:creator>Candy Randy</dc:creator>
		<pubDate>Thu, 08 Oct 2009 23:25:26 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-4055</guid>
		<description>&quot;Before iTunes and its imitators, users would play their music by navigating into folders, e.g. ‘music\artist\album\’. Today, iTunes simply presents everything in one big list that is textually filtered.&quot;

Using folders for your music is a GOOD idea, unless you&#039;re one of the masses of idiots who pretends to &#039;like&#039; music, and has to pretend to &#039;want&#039; to listen to &#039;rock&#039; today, or &#039;jazz&#039; tomorrow, thus needing iTunes and its bloody irritating &#039;filing&#039; system to find them what they pretend to &#039;want&#039; to listen to.

I know where every single song in my 4,000 track MP3 collection is, all filed in folders, either by artist, or about 10% in &#039;genre&#039; folders, such as &#039;80s&#039;, &#039;Love&#039;, &#039;Dance&#039;, etc. I don&#039;t want a long list of 4,000 tracks, thank you, that&#039;s for idiots.

Your &#039;long list&#039; idea doesn&#039;t work when you are dealing with thousands of files. I remember the position of some of the 4,000 songs SPATIALLY, i.e. I know it&#039;s in the first, top level folder, 
A-F
not in 
G-M
or whatever, and then within 
A-F
it&#039;s within
Dance
etc.

Your &#039;huge list&#039; idea is stupid. Microsoft&#039;s &#039;Ribbon&#039; is equally stupid. 

Spatial memory is where it&#039;s at. I will reveal all very soon...</description>
		<content:encoded><![CDATA[<p>&#8220;Before iTunes and its imitators, users would play their music by navigating into folders, e.g. ‘music\artist\album\’. Today, iTunes simply presents everything in one big list that is textually filtered.&#8221;</p>
<p>Using folders for your music is a GOOD idea, unless you&#8217;re one of the masses of idiots who pretends to &#8216;like&#8217; music, and has to pretend to &#8216;want&#8217; to listen to &#8216;rock&#8217; today, or &#8216;jazz&#8217; tomorrow, thus needing iTunes and its bloody irritating &#8216;filing&#8217; system to find them what they pretend to &#8216;want&#8217; to listen to.</p>
<p>I know where every single song in my 4,000 track MP3 collection is, all filed in folders, either by artist, or about 10% in &#8216;genre&#8217; folders, such as &#8217;80s&#8217;, &#8216;Love&#8217;, &#8216;Dance&#8217;, etc. I don&#8217;t want a long list of 4,000 tracks, thank you, that&#8217;s for idiots.</p>
<p>Your &#8216;long list&#8217; idea doesn&#8217;t work when you are dealing with thousands of files. I remember the position of some of the 4,000 songs SPATIALLY, i.e. I know it&#8217;s in the first, top level folder,<br />
A-F<br />
not in<br />
G-M<br />
or whatever, and then within<br />
A-F<br />
it&#8217;s within<br />
Dance<br />
etc.</p>
<p>Your &#8216;huge list&#8217; idea is stupid. Microsoft&#8217;s &#8216;Ribbon&#8217; is equally stupid. </p>
<p>Spatial memory is where it&#8217;s at. I will reveal all very soon&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Cannon</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-4039</link>
		<dc:creator>Kevin Cannon</dc:creator>
		<pubDate>Sun, 20 Sep 2009 22:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-4039</guid>
		<description>Have you seen the way the help in OSX Leopard works? It&#039;s very nice - I think you&#039;d like it.

http://www.youtube.com/watch?v=ggoTQqNXOQs</description>
		<content:encoded><![CDATA[<p>Have you seen the way the help in OSX Leopard works? It&#8217;s very nice &#8211; I think you&#8217;d like it.</p>
<p><a href="http://www.youtube.com/watch?v=ggoTQqNXOQs" rel="nofollow">http://www.youtube.com/watch?v=ggoTQqNXOQs</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forrest Landry</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-3970</link>
		<dc:creator>Forrest Landry</dc:creator>
		<pubDate>Mon, 10 Aug 2009 19:37:46 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-3970</guid>
		<description>Hi,

Perhaps some of these questions can be clarified by thinking about the interaction between user and computer as a sort of &#039;communication event&#039; embodying a &#039;language&#039;.  Implicit in a lot of discussion is the idea that there are two kinds of language of interaction: textual as implemented via the keyboard, and visual as implemented via the mouse.  Similar can be said about the information/files stored on the computer: that there are two basic kinds of stored data: document files of various kinds (readable text, source, etc) and image files (everything else -- applications, pictures, videos, music, etc).

As such, we can reformulate our questions/thoughts about effective UI design as a question about language: what is the most natural language for human interactions?  Is it a visual language or a textual one?
Note that these last questions are not about computers per se -- we could be considering a mutual dialog between two people or people and community as much as with any sort of hardware.

However, in observing actual interactions between real people, we notice immediately that while there are lots and lots of very well established textual languages (English, Spanish, French, Hindi, ect, etc), there are very very few visual languages in common usage.  Examples of visual languages include traffic lights, some types of road sign, symbols indicating bathrooms, danger, and various sorts of mapping symbols.  
Beyond that, it is fairly much admitted among professional linguists that a true visual or &quot;symbolic&quot; language is something of an oxymoron at best.  What visual language elements do exist in common usage tend to be brief, sparse in meaning content, lacking in connotative richness.  Moreover, even the most well developed symbolic/visual languages tend to have vocabularies several orders of magnitude smaller than the average vocabulary of most textual languages. 

The simple fact of the matter is that human bodies do not have an image projector built in at birth.  While we can easily receive visual images at high bandwidth, we cannot express images with similar bandwidth.  We do, however, have a voice -- an auditory projector that can generate information as well as ears to hear with.  Hence, it is *much* more natural for human beings to communicate complex information via voice (textual) than it is to communicate (interactively) similar information via any sort of image media.  The expressive bandwidth of bodily physical motion (ie,  to use a mouse pointer) is always going to be much lower than the expressive bandwidth of text (voice commands and/or keyboard usage).  The linguist perspective about actual languages in common usage merely confirms this.

Visual languages find their niche in situations where the complexity of the information to be communicated is low.  Selecting single items from small sets of available/potential items is basically the *only* situation where visual representation is preferred.  Otherwise, we see visual language used as indicators (traffic lights, stop signs, bathrooms, etc).
However, this format of communication does not scale.   As applications become more complex (as we use computers to work with ever larger amounts of data in more and more complex ways) the disparity between the carrying capacity of a visual language and a textual language grows ever more evident.  A visual language works well when there is a fairly limited set of contexts (or modes) that need to be identified.  Yet when the number of possible contexts (application states) grows without bounds, the meaning of any single visual element quickly becomes washed out (meaningless).  Attempting to identify commonalities that span all possible applications becomes an ever more difficult task as the variety of applications continues to increase, and is best avoided from the onset.

Therefore, while there will always be a niche for visual languages, it is evident that textual interactions are here to stay and are ultimately more natural for _ongoing_interactive communication_.  In situations where there is little need for back and fourth dialog/communication, visual elements work well (think presentation mediums: billboards, printed magazines, television).  For situations that require user interaction and participation (social organizations, CAD software, etc) textual representations will always dominate (either voice or keyboard).

The reality of the above paragraph is evident when you consider that the people who most vehemently promote visual models of interaction (icons, flash, 3D effects, etc) are generally business types interested in promoting (selling) a product.  Their interest is to generate only one type of interactive user response/expression: dollars spent.   The use of flashy visual elements is to entice new users into spending money, not to generate lots of continuing and ongoing dialog with the user (communication is expensive for a business).  Optimizing a UI design to get a new user to start using an application is a far different activity than optimizing a design to facilitate ongoing user interaction.   Presentation only oriented things will be visual -- interactive oriented things will ultimately be textual at their root, regardless of whatever else gets integrated with it.

Would you rather teach your children a &quot;pigden&quot; language that they can &#039;get up and running with&#039; right away, or a hard language (English) that will last them their whole lifetime?  What sort of job opportunities would you really expect to get if your entire working vocabulary consisted of only a few hundred words (a illegal alien laborer) vs. someone who had real mastery of a language (doctorate students typically have vocabularies of at least 50K words).  How obvious does it need to be that people who can type are going to be far more effective with a computer (and more employable) than people who can only operate a mouse? 

Where complexity is increasing and interactions are ongoing and long (computers are here to stay) it is clear that textual interactions with a computer are going to be ultimately better (voice commands/dialog or keyboard).  We should design with the end in mind (re &quot;7 habits&quot;) rather than continuing to even worry about the illusionary short term gains of purely visual computing.  The evidence is in and the verdict is clear: prefer textual interactions in GUI design than visual ones.  Arguments/discussion of the &quot;grandmother newbe user&quot; largely miss the point that the effort to hide complexity is itself complex and in the long run, make the situation worse for everyone.  This sort of mindset does not scale and this becomes more an more of a problem as things DO actually scale larger.

As far as the ideas of this Blog are concerned, I largely support them and have even done some work/experimentation along similar lines with varying levels of success.  I encourage further principled dialog along these lines and look forward to seeing these ideas developed further.

Forrest Landry,
San Diego, CA.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Perhaps some of these questions can be clarified by thinking about the interaction between user and computer as a sort of &#8216;communication event&#8217; embodying a &#8216;language&#8217;.  Implicit in a lot of discussion is the idea that there are two kinds of language of interaction: textual as implemented via the keyboard, and visual as implemented via the mouse.  Similar can be said about the information/files stored on the computer: that there are two basic kinds of stored data: document files of various kinds (readable text, source, etc) and image files (everything else &#8212; applications, pictures, videos, music, etc).</p>
<p>As such, we can reformulate our questions/thoughts about effective UI design as a question about language: what is the most natural language for human interactions?  Is it a visual language or a textual one?<br />
Note that these last questions are not about computers per se &#8212; we could be considering a mutual dialog between two people or people and community as much as with any sort of hardware.</p>
<p>However, in observing actual interactions between real people, we notice immediately that while there are lots and lots of very well established textual languages (English, Spanish, French, Hindi, ect, etc), there are very very few visual languages in common usage.  Examples of visual languages include traffic lights, some types of road sign, symbols indicating bathrooms, danger, and various sorts of mapping symbols.<br />
Beyond that, it is fairly much admitted among professional linguists that a true visual or &#8220;symbolic&#8221; language is something of an oxymoron at best.  What visual language elements do exist in common usage tend to be brief, sparse in meaning content, lacking in connotative richness.  Moreover, even the most well developed symbolic/visual languages tend to have vocabularies several orders of magnitude smaller than the average vocabulary of most textual languages. </p>
<p>The simple fact of the matter is that human bodies do not have an image projector built in at birth.  While we can easily receive visual images at high bandwidth, we cannot express images with similar bandwidth.  We do, however, have a voice &#8212; an auditory projector that can generate information as well as ears to hear with.  Hence, it is *much* more natural for human beings to communicate complex information via voice (textual) than it is to communicate (interactively) similar information via any sort of image media.  The expressive bandwidth of bodily physical motion (ie,  to use a mouse pointer) is always going to be much lower than the expressive bandwidth of text (voice commands and/or keyboard usage).  The linguist perspective about actual languages in common usage merely confirms this.</p>
<p>Visual languages find their niche in situations where the complexity of the information to be communicated is low.  Selecting single items from small sets of available/potential items is basically the *only* situation where visual representation is preferred.  Otherwise, we see visual language used as indicators (traffic lights, stop signs, bathrooms, etc).<br />
However, this format of communication does not scale.   As applications become more complex (as we use computers to work with ever larger amounts of data in more and more complex ways) the disparity between the carrying capacity of a visual language and a textual language grows ever more evident.  A visual language works well when there is a fairly limited set of contexts (or modes) that need to be identified.  Yet when the number of possible contexts (application states) grows without bounds, the meaning of any single visual element quickly becomes washed out (meaningless).  Attempting to identify commonalities that span all possible applications becomes an ever more difficult task as the variety of applications continues to increase, and is best avoided from the onset.</p>
<p>Therefore, while there will always be a niche for visual languages, it is evident that textual interactions are here to stay and are ultimately more natural for _ongoing_interactive communication_.  In situations where there is little need for back and fourth dialog/communication, visual elements work well (think presentation mediums: billboards, printed magazines, television).  For situations that require user interaction and participation (social organizations, CAD software, etc) textual representations will always dominate (either voice or keyboard).</p>
<p>The reality of the above paragraph is evident when you consider that the people who most vehemently promote visual models of interaction (icons, flash, 3D effects, etc) are generally business types interested in promoting (selling) a product.  Their interest is to generate only one type of interactive user response/expression: dollars spent.   The use of flashy visual elements is to entice new users into spending money, not to generate lots of continuing and ongoing dialog with the user (communication is expensive for a business).  Optimizing a UI design to get a new user to start using an application is a far different activity than optimizing a design to facilitate ongoing user interaction.   Presentation only oriented things will be visual &#8212; interactive oriented things will ultimately be textual at their root, regardless of whatever else gets integrated with it.</p>
<p>Would you rather teach your children a &#8220;pigden&#8221; language that they can &#8216;get up and running with&#8217; right away, or a hard language (English) that will last them their whole lifetime?  What sort of job opportunities would you really expect to get if your entire working vocabulary consisted of only a few hundred words (a illegal alien laborer) vs. someone who had real mastery of a language (doctorate students typically have vocabularies of at least 50K words).  How obvious does it need to be that people who can type are going to be far more effective with a computer (and more employable) than people who can only operate a mouse? </p>
<p>Where complexity is increasing and interactions are ongoing and long (computers are here to stay) it is clear that textual interactions with a computer are going to be ultimately better (voice commands/dialog or keyboard).  We should design with the end in mind (re &#8220;7 habits&#8221;) rather than continuing to even worry about the illusionary short term gains of purely visual computing.  The evidence is in and the verdict is clear: prefer textual interactions in GUI design than visual ones.  Arguments/discussion of the &#8220;grandmother newbe user&#8221; largely miss the point that the effort to hide complexity is itself complex and in the long run, make the situation worse for everyone.  This sort of mindset does not scale and this becomes more an more of a problem as things DO actually scale larger.</p>
<p>As far as the ideas of this Blog are concerned, I largely support them and have even done some work/experimentation along similar lines with varying levels of success.  I encourage further principled dialog along these lines and look forward to seeing these ideas developed further.</p>
<p>Forrest Landry,<br />
San Diego, CA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicholas Harris</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-3957</link>
		<dc:creator>Nicholas Harris</dc:creator>
		<pubDate>Wed, 05 Aug 2009 20:05:37 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-3957</guid>
		<description>I worry that most users are too lazy to tag.

Are we expected to upload all our documents to &quot;the cloud&quot; where a computer can compare their topics based on their summaries and tag them for us? Would we not worry about the security of our private data?

Do we need hierarchical ontologies after all?

In your linked Clay Shirky video he talked about Flickr users tagging photographs which could be retrieved by the filter: &quot;cats in sinks&quot;. You implied that this was superior to a hierarchical filing system which would have be categorized (no pun intended) as either cats/sinks, or sinks/cats. Yet, as soon as I read this I wondered about:

&quot;kittens in sinks&quot;

Surely the system should know that a kitten is a kind of cat and whilst placing a priority on Flickr photographs tagged with &quot;kitten&quot; and &quot;sink&quot; it should also include &quot;cat&quot; (which is a conceptual generality of the specific &#039;kitten&#039; class, in other words a &quot;superclass&quot;, ontologically-speaking) as it may otherwise yield zero hits for being too specific.

&#039;Yes, we particularly want kittens, but we would accept cats, some of which may turn out to be kittens in sinks tagged incorrectly as cats in basins.&#039;

Who gets to decide upon the structure of this ontology? What are its political ramifications? Perhaps, the imprecision of any such interface could be helped by making it conversational... approximating iteratively to a point of common understanding between man and machine. Rather than expecting it to know what we mean on the first attempt.</description>
		<content:encoded><![CDATA[<p>I worry that most users are too lazy to tag.</p>
<p>Are we expected to upload all our documents to &#8220;the cloud&#8221; where a computer can compare their topics based on their summaries and tag them for us? Would we not worry about the security of our private data?</p>
<p>Do we need hierarchical ontologies after all?</p>
<p>In your linked Clay Shirky video he talked about Flickr users tagging photographs which could be retrieved by the filter: &#8220;cats in sinks&#8221;. You implied that this was superior to a hierarchical filing system which would have be categorized (no pun intended) as either cats/sinks, or sinks/cats. Yet, as soon as I read this I wondered about:</p>
<p>&#8220;kittens in sinks&#8221;</p>
<p>Surely the system should know that a kitten is a kind of cat and whilst placing a priority on Flickr photographs tagged with &#8220;kitten&#8221; and &#8220;sink&#8221; it should also include &#8220;cat&#8221; (which is a conceptual generality of the specific &#8216;kitten&#8217; class, in other words a &#8220;superclass&#8221;, ontologically-speaking) as it may otherwise yield zero hits for being too specific.</p>
<p>&#8216;Yes, we particularly want kittens, but we would accept cats, some of which may turn out to be kittens in sinks tagged incorrectly as cats in basins.&#8217;</p>
<p>Who gets to decide upon the structure of this ontology? What are its political ramifications? Perhaps, the imprecision of any such interface could be helped by making it conversational&#8230; approximating iteratively to a point of common understanding between man and machine. Rather than expecting it to know what we mean on the first attempt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Spears</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-3955</link>
		<dc:creator>Nathan Spears</dc:creator>
		<pubDate>Wed, 05 Aug 2009 15:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-3955</guid>
		<description>It seems worth mentioning that even the commenters who don&#039;t like any of your ideas aren&#039;t bothering to defend the broken aspects of Windows that you are criticizing.  The point I think most of them are missing is that some adaptation to a new system is inevitable.  It feels easy to click on things on the desktop now after decades of doing so, but that &quot;discoverable&quot; behavior isn&#039;t any more natural than typing in a command line.  A well designed command line would be discoverable, and easier to use.  Just because gmail&#039;s label and search features aren&#039;t all you want them to be yet doesn&#039;t mean the ideas of label and search are bunk.</description>
		<content:encoded><![CDATA[<p>It seems worth mentioning that even the commenters who don&#8217;t like any of your ideas aren&#8217;t bothering to defend the broken aspects of Windows that you are criticizing.  The point I think most of them are missing is that some adaptation to a new system is inevitable.  It feels easy to click on things on the desktop now after decades of doing so, but that &#8220;discoverable&#8221; behavior isn&#8217;t any more natural than typing in a command line.  A well designed command line would be discoverable, and easier to use.  Just because gmail&#8217;s label and search features aren&#8217;t all you want them to be yet doesn&#8217;t mean the ideas of label and search are bunk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: maik</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-3952</link>
		<dc:creator>maik</dc:creator>
		<pubDate>Tue, 04 Aug 2009 23:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-3952</guid>
		<description>Isn&#039;t the next logical and natural extension to this telling your computer what to do via voice commands?</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t the next logical and natural extension to this telling your computer what to do via voice commands?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Callie</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-3950</link>
		<dc:creator>Callie</dc:creator>
		<pubDate>Tue, 04 Aug 2009 17:00:52 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-3950</guid>
		<description>*Addendum: how long will it take for her to search for everything that she wants to do on her computer by keyword, I meant! :)</description>
		<content:encoded><![CDATA[<p>*Addendum: how long will it take for her to search for everything that she wants to do on her computer by keyword, I meant! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Callie</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-3949</link>
		<dc:creator>Callie</dc:creator>
		<pubDate>Tue, 04 Aug 2009 16:59:35 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-3949</guid>
		<description>The extremities of these replies are examples to me of what I have learned in my UI studies this year - that different users learn and execute their work flows in different ways. It looks like your searching/filtering/tagging mechanism might work well for a significant percentage of people (especially the following: advanced users, programmers, people who spend a lot of time on their computer, people who think primarily textually) and not as well for another large percentage of people (beginning to intermediate users, people who do not spend much time on a computer, people who think visually). 

Having multiple routes to discovery enables users to find the path they feel most comfortable with, and more quickly discover what they can do in the OS/application. As some have mentioned, some users prefer the mouse, or thinking categorically or visually. My favorite thing about items like the OSX spotlight vs. finder/dock/shortcuts or Vista&#039;s co-compatibility with searching or sorting into folders is that users can choose what they feel comfortable with. Even though I have had the spotlight search for years on my mac (and it is beautiful and sometimes I use it), my spatial recognition is stronger and I often access applications or items by remembering where they are on the desktop or dock. Accomodation of spatial/visual thinking is just as important as intelligent  &quot;keyword&quot; searching/filtering.

I agree that needless categorization sometimes plagues our electronic efficiency and ease of use. But even an intelligent command line is more of a programmer&#039;s solution. I can teach my mother to use Google in only a few seconds, but how long will it take for her to search by keyword? Multiple avenues of discovery are valuable. Please don&#039;t leave the spatial thinkers out in the cold. :)

Loved the article!</description>
		<content:encoded><![CDATA[<p>The extremities of these replies are examples to me of what I have learned in my UI studies this year &#8211; that different users learn and execute their work flows in different ways. It looks like your searching/filtering/tagging mechanism might work well for a significant percentage of people (especially the following: advanced users, programmers, people who spend a lot of time on their computer, people who think primarily textually) and not as well for another large percentage of people (beginning to intermediate users, people who do not spend much time on a computer, people who think visually). </p>
<p>Having multiple routes to discovery enables users to find the path they feel most comfortable with, and more quickly discover what they can do in the OS/application. As some have mentioned, some users prefer the mouse, or thinking categorically or visually. My favorite thing about items like the OSX spotlight vs. finder/dock/shortcuts or Vista&#8217;s co-compatibility with searching or sorting into folders is that users can choose what they feel comfortable with. Even though I have had the spotlight search for years on my mac (and it is beautiful and sometimes I use it), my spatial recognition is stronger and I often access applications or items by remembering where they are on the desktop or dock. Accomodation of spatial/visual thinking is just as important as intelligent  &#8220;keyword&#8221; searching/filtering.</p>
<p>I agree that needless categorization sometimes plagues our electronic efficiency and ease of use. But even an intelligent command line is more of a programmer&#8217;s solution. I can teach my mother to use Google in only a few seconds, but how long will it take for her to search by keyword? Multiple avenues of discovery are valuable. Please don&#8217;t leave the spatial thinkers out in the cold. :)</p>
<p>Loved the article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-3947</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 04 Aug 2009 02:28:44 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-3947</guid>
		<description>Reading this article I quickly realized how much I think QuickSilver for Mac is like the AwesomeBar in that it is a frequency/relevancy list for launching programs you use (or lesser ones you may have just installed or never used).

http://quicksilver.en.softonic.com/</description>
		<content:encoded><![CDATA[<p>Reading this article I quickly realized how much I think QuickSilver for Mac is like the AwesomeBar in that it is a frequency/relevancy list for launching programs you use (or lesser ones you may have just installed or never used).</p>
<p><a href="http://quicksilver.en.softonic.com/" rel="nofollow">http://quicksilver.en.softonic.com/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
