<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <title>Nimble Code: Great Picture, But One Quibble</title>
  <subtitle type="html">Jacob Harris' Weblog</subtitle>
  <id>tag:www.nimblecode.com,2005:Typo</id>
  <generator version="4.0" uri="http://typo.leetsoft.com">Typo</generator>
  <link href="http://www.nimblecode.com/xml/atom10/article/47/feed.xml" rel="self" type="application/xml+atom"/>
  <link href="http://www.nimblecode.com/articles/2005/09/30/great-picture-but-one-quibble" rel="alternate" type="text/html"/>
  <updated>2006-02-21T21:00:07-08:00</updated>
  <entry>
    <author>
      <name>Amy Hoy</name>
    </author>
    <id>urn:uuid:e235de6b-c51a-4a3a-81ae-39ca4eb8d477</id>
    <published>2005-10-07T17:41:56-07:00</published>
    <updated>2006-02-21T21:00:07-08:00</updated>
    <title>Comment on Great Picture, But One Quibble by Amy Hoy</title>
    <link href="http://www.nimblecode.com/articles/2005/09/30/great-picture-but-one-quibble#comment-57" rel="alternate" type="text/html"/>
    <content type="html">&lt;p&gt;I totally agree with you about &lt;span class="caps"&gt;RSS&lt;/span&gt;. I think that for the tech superstars like O&amp;#8217;Reilly, it&amp;#8217;s already entered the passé phase. But &lt;span class="caps"&gt;RSS&lt;/span&gt; for stuff other than blog updates is a newish and very exciting thing driving all that openness. All that openness wouldn&amp;#8217;t have gotten started without &lt;span class="caps"&gt;RSS&lt;/span&gt;, I think.&lt;/p&gt;</content>
  </entry>
  <entry>
    <author>
      <name>Jacob Harris</name>
      <email>harrisj@nimblecode.com</email>
    </author>
    <id>urn:uuid:21e83a8e0820389c1fe331156a4bdf60</id>
    <published>2005-09-30T00:09:00-07:00</published>
    <updated>2008-11-19T18:19:23-08:00</updated>
    <title>Great Picture, But One Quibble</title>
    <link href="http://www.nimblecode.com/articles/2005/09/30/great-picture-but-one-quibble" rel="alternate" type="text/html"/>
    <category term="web" scheme="http://www.nimblecode.com/articles/category/47" label="Web"/>
    <category term="web-services" scheme="http://www.nimblecode.com/articles/category/47" label="Web Services"/>
    <category term="web2.0" scheme="http://www.nimblecode.com/articles/tag"/>
    <category term="rss" scheme="http://www.nimblecode.com/articles/tag"/>
    <content type="html">&lt;div style="float:left; padding-right: 0.5em;" class="flickrplugin"&gt;&lt;a href="http://www.flickr.com/photos/36521959321@N01/44349798"&gt;&lt;img src="http://static.flickr.com/28/44349798_0e487287bc_s.jpg" width="75" height="75" alt="Web2MemeMap" title="Web2MemeMap"/&gt;&lt;/a&gt;&lt;/div&gt; Courtesy of Tim O&amp;#8217;Reilly&amp;#8217;s &lt;a href="http://wiki.oreillynet.com/foocamp05/index.cgi"&gt;Foo Camp&lt;/a&gt; (which I am definitely not cool enough to be invited to), there is now a picture to match the exciting flow of ideas and themes coalescing into &lt;strong&gt;Web 2.0&lt;/strong&gt;. I think this assemblage of bubbles and trends is a great thing to see, especially since it serves as a better executive summary of high-level ideas than gleaning bits and pieces of the big picture from blogs and demo sites across the web.

	&lt;p&gt;That said, I think one thing is missing from the picture they provide. Maybe I am a bit &lt;a href="/articles/tag/rss"&gt;preoccupied&lt;/a&gt; with the subject, but I think &lt;span class="caps"&gt;RSS &lt;/span&gt;(&lt;em&gt;or Atom here, I&amp;#8217;m just using &lt;span class="caps"&gt;RSS&lt;/span&gt; as shorthand for syndication&lt;/em&gt;) is really one of the biggest things driving Web2.0 services and adoption these days, but it hasn&amp;#8217;t even gotten a mention in the top as an influencing technology (unlike blogs or Gmail). I think blogs were great at establishing &lt;span class="caps"&gt;RSS&lt;/span&gt; as a way of keeping track of changes, but the really influential aspect of Del.icio.us and Flickr is not just tagging, but establishing &lt;span class="caps"&gt;RSS&lt;/span&gt; as a &lt;a href="/articles/2005/09/23/rss-comes-to-the-enterprise"&gt;mechanism for tracking any possible view of the system you might want&lt;/a&gt; in as light-weight and user-friendly mechanism as possible (as opposed to the awkwardness of &lt;span class="caps"&gt;SOAP&lt;/span&gt; or even &lt;span class="caps"&gt;REST&lt;/span&gt; to the end user).&lt;/p&gt;


	&lt;p&gt;I think the source of my unease here is that I&amp;#8217;m mostly a backend guy. A lot of my work at Alacra has been making sure that all sorts of information flows agilely between processes and servers. Backend stuff. It makes it happen, but if it&amp;#8217;s working, you never notice how critical it is to success. Similarly, &lt;span class="caps"&gt;AJAX&lt;/span&gt; and other front-end browser mechanisms are very nice in my mind. But the biggest joys and successes of Web2.0 are all driven by the fluidity and ease of &lt;span class="caps"&gt;RSS&lt;/span&gt; and &lt;span class="caps"&gt;REST&lt;/span&gt;. &amp;#8220;Hackability&amp;#8221;, &amp;#8220;Data as Intel Inside&amp;#8221;, &amp;#8220;Right to Remix&amp;#8221; ... &lt;span class="caps"&gt;RSS&lt;/span&gt; made this a possibility and these are what drives me to take Web2.0 seriously and not just as another wave of web hype. All I&amp;#8217;m asking for is a little recognition. Thanks.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; The good news is that it seems like I&amp;#8217;m not alone in this view. The bad news is my company is &lt;a href="http://archive.scripting.com/2005/09/27#web20IsReallySimple"&gt;Dave Winer&lt;/a&gt;.&lt;/p&gt;</content>
  </entry>
</feed>
