<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Depth-First: Tag humanized</title>
    <link>http://depth-first.com/articles/tag/humanized</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Walking the Web of Chemical Informatics</description>
    <item>
      <title>Do You Use the Command Line?</title>
      <description>&lt;blockquote&gt;
    &lt;p&gt;&lt;a href="http://flickr.com/photos/bartholomule/65432558/"&gt;&lt;img src="http://depth-first.com/demo/20070315/keyboard.jpg" align="right" border="0"&gt;&lt;/img&gt;&lt;/a&gt;In the run to abandon command line interfaces for the GUI, we've left behind the versatility of language.&lt;/p&gt;
    
    &lt;p&gt;...&lt;/p&gt;
    
    &lt;p&gt;[Imagine] using a drop-down menu to select the one web site you want to go to out of the 100 million web sites in existence. Ludicrous! How do we actually surf to a site? By typing an address into the address bar. When we want to go to the mail "application", we type in "gmail.com"; when we want to open a news "application", we type in "nytimes.com". On the old unix command lines, we would type type "pine" and "rn". See a similarity? The address bar is just a primitive command line. A command line that your grandmother can&#8212;and does&#8212;use.&lt;/p&gt;
    
    &lt;p&gt;-&lt;cite&gt;Aza Raskin, &lt;a href="http://www.humanized.com/weblog/2007/02/24/your_grandmothers_command_line_the_command_line_co/"&gt;Get Humanized&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The command line is alive and well. It's simply become so sophisticated that most of us don't realize we're using it. Whether we're entering a URL into a browser address bar, taking advantage of autocomplete to look up a co-worker's name in an address book, or using Google to search the Web, the command line is hard at work. Most people wouldn't want it any other way.&lt;/p&gt;

&lt;p&gt;To an end user, a command line is nothing more than a box to enter text. The magic happens when this text is processed. Aza Raskin's company &lt;a href="http://humanized.com"&gt;Humanized&lt;/a&gt; uses this simple idea to build text-driven applications that save time and effort. &lt;/p&gt;

&lt;p&gt;What would happen if the same thinking were applied to chemical informatics?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Image credit: &lt;a href="http://flickr.com/photos/bartholomule/"&gt;Bartholomule&lt;/a&gt; - &lt;a href="http://flickr.com"&gt;Flickr&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;</description>
      <pubDate>Thu, 15 Mar 2007 11:18:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:5ae758c1-3e43-42fb-81ad-7aca498bea13</guid>
      <author>Rich Apodaca</author>
      <link>http://depth-first.com/articles/2007/03/15/do-you-use-the-command-line</link>
      <category>Meta</category>
      <category>humanized</category>
      <category>commandline</category>
      <category>text</category>
    </item>
  </channel>
</rss>
