<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>doodleporn - Latest Comments in For the Love of the Command Line</title><link>http://doodleporn.disqus.com/</link><description></description><atom:link href="https://doodleporn.disqus.com/for_the_love_of_the_command_line/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sun, 08 Mar 2009 14:38:47 -0000</lastBuildDate><item><title>Re: For the Love of the Command Line</title><link>http://doodleporn.tumblr.com/post/84647876#comment-6997021</link><description>&lt;p&gt;From the beginning of Twitter, I've seen a huge ammount of its power locked up in being more of a platform than a messaging service.&lt;/p&gt;&lt;p&gt;I built &lt;a href="http://mytwitternotebook.com" rel="nofollow noopener" target="_blank" title="mytwitternotebook.com"&gt;mytwitternotebook.com&lt;/a&gt; (and a couple other of my own utilities) on that idea; that twitter was something that you could get at from your desk and your phone, and that in itself lends an opportunity to interact in interesting ways.&lt;/p&gt;&lt;p&gt;The command line aspects of it are both awesome and frustrating.  You are unambiguous about what you want, and what you're getting back (a programmer's dream); but even for return data, you're limited to 140 characters, in that respect, it's nothing like a quality command line.  You also can't do any kind of mashups with commands (In unix they called them pipes...mashups aren't a new idea at all)  but you can't get what you want if you go like this&lt;/p&gt;&lt;p&gt;  d stock AAPL | d tweetnote #stock&lt;/p&gt;&lt;p&gt;That would just confuse @stock, not send the stock to your personal notebook;&lt;/p&gt;&lt;p&gt;Twitter is at best a decent starting point for a mobile, shared command line.  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">issackelly</dc:creator><pubDate>Sun, 08 Mar 2009 14:38:47 -0000</pubDate></item></channel></rss>