<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

    <channel>
      <title>Hang Ten</title>
      <link>http://rubywaves.com/blog/hang-ten.rss</link>
      <description />
      <language>en</language>

        <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/HangTen" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		  <title>GoRuCo Rocked</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/ymD4YAIGJxA/goruco-rocks</link>
          <pubDate>Sat, 06 Jun 2009 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;First, for those of you who haven&amp;#8217;t heard, &lt;a href="http://dev.zeraweb.com/moving-on"&gt;I&amp;#8217;ve left AT&amp;amp;T Interactive and am now with new startup, SharesPost.com&lt;/a&gt;. (&lt;a href="http://sharespost.com/"&gt;Launch is coming soon.&lt;/a&gt;) And, no, it isn&amp;#8217;t running on Waves. At least, not yet. More on this momentarily.&lt;/p&gt;
&lt;p&gt;Second, some thoughts on the recent &lt;a href="http://goruco.com"&gt;GoRuCo&lt;/a&gt;, held at Pace University in Manhattan &amp;#8230; to begin with, awesome. &lt;em&gt;That&lt;/em&gt; is how you do it. I haven&amp;#8217;t been to all the regional RubyConfs, but I&amp;#8217;ve been to several, as well as the national conference, and many smaller non-Ruby conferences. They all tend to suffer from one common malady: too many talks and too little socializing. Furthermore, there just aren&amp;#8217;t enough women involved. I realize &lt;a href="http://www.sarahmei.com/blog/?p=46"&gt;this has become topical lately&lt;/a&gt;, but I&amp;#8217;ve always thought the imbalance in the technical world (not just Ruby Nation) was ridiculous.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/goruco-rocks</feedburner:origLink></item>
        <item>
		  <title>REST FTW, Part 3</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/tOPCgV7ynIU/rest-ftw-part-3</link>
          <pubDate>Sun, 03 May 2009 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;In &lt;a href="/rest-ftw-2"&gt;my last post&lt;/a&gt;, I suggested thinking about REST and ROA in the context of an object-based platform and protocol neutral approach to distributed computing. The "objects" are the specific representations (MP3, JSON, HTML) of a resource. The semantics of a resource itself are intentionally vague because you never interact with them directly, at least from the standpoint of ROA. This ensures that the "platform neutral" part of the bargain is never compromised.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/rest-ftw-part-3</feedburner:origLink></item>
        <item>
		  <title>REST FTW, Part 2</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/FYJxZYCYmHM/rest-ftw-part-2</link>
          <pubDate>Tue, 21 Apr 2009 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;REST is
not an architecture, but a set of constraints for an architecture. I
like to use the phrase &lt;em&gt;Resource-Oriented Architecture&lt;/em&gt; to talk
about the specific Web-based architecture that satisfies those
constraints. But the main thing to remember is that these are
constraints &lt;em&gt;for a bandwidth-optimizing object-based distributed computing architecture that is both platform and protocol neutral&lt;/em&gt;.
In that light, one thing that should be clear is that REST therefore
applies to pretty much everything Web developers do these days.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/rest-ftw-part-2</feedburner:origLink></item>
        <item>
		  <title>REST FTW, Part 1</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/X29uVwxCkWs/rest-ftw-part-1</link>
          <pubDate>Tue, 21 Apr 2009 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;Lately, in my talks on Waves and how it supports RESTful architectures, I've found I've had to take a step back and talk more about what REST is and why it matters.&lt;/p&gt;

&lt;p&gt;This is a bit surprising, since REST has been on the buzzword bingo card for years now. However, it turns out that most of what has passed for RESTful is really what I have come to call &lt;em&gt;REST-lite&lt;/em&gt;. Essentially, REST-lite focused on the verbs of the HTTP protocol and (more or less) ignores ... well, the rest.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/rest-ftw-part-1</feedburner:origLink></item>
        <item>
		  <title>Speaking At GoRuCo</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/BTXJEHAhH7s/speaking-at-goruco</link>
          <pubDate>Sun, 05 Apr 2009 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;I&amp;#8217;m very happy to announce that I&amp;#8217;ll be speaking on Waves at &lt;a href="goruco"&gt;GoRuCo&lt;/a&gt; in The Big Apple (specifically, Pace University in Lower Manhattan) on May 31st. I love Manhattan (or, at least, I love visiting there) and I really enjoy these smaller conferences. I wanted to speak at last year&amp;#8217;s GoRuCo but narrowly missed the deadline because I had been completely immersed in getting the first version of Waves out the door.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/speaking-at-goruco</feedburner:origLink></item>
        <item>
		  <title>LA RubyConf Kills It</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/BmMxPa6wguY/la-rubyconf-kills-it</link>
          <pubDate>Sun, 05 Apr 2009 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;The inaugural LA RubyConf was a bit hit. I am proud to have kicked things off as the first speaker, given the line-up that followed, which included &lt;a href="http://github.com/jbarnette/johnson/tree/master"&gt;cats and dogs living together&lt;/a&gt;, &lt;a href="http://deadprogrammersociety.blogspot.com/2009/03/project-flying-robot-i-believe-i-can.html"&gt;flying robots&lt;/a&gt;, &lt;a href="http://poolpartyrb.com/"&gt;cloud comedy&lt;/a&gt; and a &lt;a href="http://onestepback.org/"&gt;unified theory of hacking&lt;/a&gt;.&lt;/p&gt;



          </description>
        <feedburner:origLink>http://rubywaves.com/la-rubyconf-kills-it</feedburner:origLink></item>
        <item>
		  <title>When Waves Grows Up</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/VjnN-SYMLKo/when-waves-grows-up</link>
          <pubDate>Fri, 13 Mar 2009 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;I get a number of questions along the lines of, &amp;#8220;Why shouldn&amp;#8217;t I just use Rails or Merb? How is Waves better than Rails?&amp;#8221; and so forth. The thing is, Waves is not &amp;#8220;a better Rails&amp;#8221; &amp;#8212; Rails does a great job for database-driven Web apps and Merb provides a nice target for &amp;#8220;Rails 3&amp;#8221;. Waves is trying to solve a different problem entirely.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/when-waves-grows-up</feedburner:origLink></item>
        <item>
		  <title>Waves Rumors</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/EJwPP5LAToc/waves-rumors</link>
          <pubDate>Sat, 07 Mar 2009 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;No big news, but I thought someone needed to update the blog, since we have been hard at work hacking Waves. Luckily the commits always tell the truth, which is that there are interesting new features coming out with the (imminent) 0.83 release of Waves.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/waves-rumors</feedburner:origLink></item>
        <item>
		  <title>Waves Begins The New Year</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/DuIYywqSaf4/updated-roadmap</link>
          <pubDate>Tue, 20 Jan 2009 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;You can watch my &lt;a href="http://is.gd/gDpf"&gt;RubyConf presentation&lt;/a&gt; now, or just &lt;a href="http://www.slideshare.net/dyoder/rubyconf-preso"&gt;go through the slides&lt;/a&gt; to better understand what we&amp;#8217;re doing here.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/updated-roadmap</feedburner:origLink></item>
        <item>
		  <title>We’re Now AT&amp;T Interactive</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/naJVMeO13qY/att-announcement</link>
          <pubDate>Tue, 20 Jan 2009 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;This is a little bit late, but I wanted to let everybody know that we&amp;#8217;re now AT&amp;amp;T Interactive. Our work today encompasses everything from &lt;a href="http://speak4it.com/"&gt;voice recognition&lt;/a&gt; to social networking. We&amp;#8217;ve recently hired Chris Hughes (not &lt;a href="http://is.gd/Nc7"&gt;that one&lt;/a&gt;, &lt;a href="http://is.gd/gBQr"&gt;this one&lt;/a&gt;), &lt;a href="http://labs.citrusbyte.com/poolparty"&gt;Ari Lerner&lt;/a&gt;, and &lt;a href="http://www.ohloh.net/p/rubinius/contributors/16361677958936"&gt;Eero Saynatkari&lt;/a&gt;, along with many other talented folks.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/att-announcement</feedburner:origLink></item>
        <item>
		  <title>Waves 0.8.1</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/PkCsyvfGews/0-8-1</link>
          <pubDate>Fri, 07 Nov 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;This is mostly a stablization release from the big 0.8.0 release last week. The big improvement is actually the docs, most of which are on this Web site.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/0-8-1</feedburner:origLink></item>
        <item>
		  <title>Why Resource-Oriented Matters</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/k6jFmKzQmas/why-resource-oriented-matters</link>
          <pubDate>Thu, 06 Nov 2008 00:00:00 +0000</pubDate>
          <description>
            
          </description>
        <feedburner:origLink>http://rubywaves.com/why-resource-oriented-matters</feedburner:origLink></item>
        <item>
		  <title>Waves 0.8.0</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/lyoCjP--FzQ/0-8-0</link>
          <pubDate>Sun, 02 Nov 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;So what have we been up to? The biggest change is that the overall focus has shifted from Sun &lt;span class="caps"&gt;MVC&lt;/span&gt; with support for alternative approaches to being much more resource-oriented and architecturally focused. Sun &lt;span class="caps"&gt;MVC&lt;/span&gt; is now basically one way to use Waves, but there is nothing special about it.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/0-8-0</feedburner:origLink></item>
        <item>
		  <title>Speaking At RubyConf</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/PMyREXc4k9Q/speaking-at-rubyconf</link>
          <pubDate>Tue, 21 Oct 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;I am very excited to be speaking at RubyConf &amp;#8216;08. It is sold out, but if you&amp;#8217;re going, don&amp;#8217;t hesitate to drop me a line. If you&amp;#8217;re not, I will be posting the slides here and of course Confreaks is recording the sessions.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/speaking-at-rubyconf</feedburner:origLink></item>
        <item>
		  <title>Waves 0.7.7 (Briareus)</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/Eefn7SQIaAU/waves-0-7-7</link>
          <pubDate>Fri, 11 Jul 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;More good news: we now have version 0.7.7 (&lt;a href="http://waves.lighthouseapp.com/projects/10707/milestones/13337-0-7-7-briareus"&gt;Briareus&lt;/a&gt;) available as a gem. Kudos to Matthew King, who did the bulk of the work on this release (and the &lt;a href="http://waves.lighthouseapp.com/projects/10707/milestones/12837-0-7-6-eris"&gt;last one&lt;/a&gt;, which happened so quickly, I never even got a chance to blog about it). This makes three releases in the past month, somewhat making up for the long stretch between 0.7.3 and the next really meaningful release, 0.7.5. Not only that, but we have our new resource-oriented mappings in edge, just waiting to find their way into the world. So you can continue to expect us to keep the pace.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/waves-0-7-7</feedburner:origLink></item>
        <item>
		  <title>Waves 0.7.5 (Janus)</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/65HVsaaIZns/waves-0-7-5</link>
          <pubDate>Thu, 19 Jun 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;Waves is an open source framework for building web applications in Ruby, built from a smashing combination of mapping lambdas for request routing and just-in-time resources for request processing.  Waves doesn&amp;#8217;t care which &lt;span class="caps"&gt;ORM&lt;/span&gt;, template renderer, or Rack handler you use.  Waves is thread-safe when you want it to be.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/waves-0-7-5</feedburner:origLink></item>
        <item>
		  <title>Speaking At LoneStar RubyConf And Other News</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/pBf_RQBj2yw/lonestar-announcement</link>
          <pubDate>Mon, 16 Jun 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;Good news! I&amp;#8217;ve been selected to speak at the LoneStar RubyConf in Austin, TX, September 4-6, 2008 on Resource-oriented Web apps using Waves. This will be perfect timing as we expect to have our entire Resource-driven, Layers-based goodness ready for show (also known as the &lt;a href="http://waves.lighthouseapp.com/projects/10707-waves/milestones"&gt;Turtles All The Way Down release&lt;/a&gt;). Hope to see you there!&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/lonestar-announcement</feedburner:origLink></item>
        <item>
		  <title>Dan Signs On With <span class="caps">YPC</span></title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/ygV3lqfzGOw/ive-joined-yellowpagescom</link>
          <pubDate>Sun, 18 May 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;As many of you may already know, &lt;span class="caps"&gt;YPC&lt;/span&gt; is one of the largest (if not &lt;em&gt;the&lt;/em&gt; largest) Ruby / Rails deployments in the world. &lt;span class="caps"&gt;YPC&lt;/span&gt; &lt;span class="caps"&gt;SRD&lt;/span&gt; is thus one of the few places where you can work with Ruby on innovative and exciting projects. We are also hiring, so if this sounds interesting, and you&amp;#8217;d like to be able to work with technologies like Waves, &lt;a href="mailto:dan@zeraweb.com"&gt;hit me up&lt;/a&gt;.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/ive-joined-yellowpagescom</feedburner:origLink></item>
        <item>
		  <title>We’ve Gone Git!</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/19027UHOj7c/official-move-to-git</link>
          <pubDate>Tue, 25 Mar 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;We&amp;#8217;ve joined the cool kids and gone all &lt;a href="http://github.com/dyoder/waves/tree/master"&gt;git&lt;/a&gt;, so if you&amp;#8217;ve been using the &lt;span class="caps"&gt;SVN&lt;/span&gt; repo, stop, drop, and roll. If you have questions about how to use Git or transition from &lt;span class="caps"&gt;SVN&lt;/span&gt; to Git, please &lt;a href="http://groups.google.com/group/rubywaves"&gt;stop by the forum&lt;/a&gt;, and we&amp;#8217;ll do our best to help!&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/official-move-to-git</feedburner:origLink></item>
        <item>
		  <title>Waves Featured On InfoQ / RubyInside</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/6p9NKyN0thM/waves-on-infoq-and-rubyinside</link>
          <pubDate>Mon, 03 Mar 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;Well, &lt;em&gt;that&lt;/em&gt; happened. On consecutive days, Waves was featured on two popular Ruby blogs, &lt;a href="http://www.infoq.com/ruby/"&gt;InfoQ&lt;/a&gt; and Peter Cooper&amp;#8217;s &lt;a href="http://www.rubyinside.com/"&gt;RubyInside&lt;/a&gt;. It was fantastic exposure and a great way to cap of Waves&amp;#8217; first month since it&amp;#8217;s public launch.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/waves-on-infoq-and-rubyinside</feedburner:origLink></item>
        <item>
		  <title>Just In Time Resources And Why They Matter</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/zkle6zY-HBE/just-in-time-resources</link>
          <pubDate>Sat, 16 Feb 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;One of the things I always found myself doing in Rails was refactoring my models and controllers so that I could create new ones by simply inheriting from an appropriate base class and then maybe add a few tweaks and be finished. I typically ended up with three or four base classes representing different types of resources. For example, I might have one for administrative-related controllers, another for content-delivery related controllers, and so on.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/just-in-time-resources</feedburner:origLink></item>
        <item>
		  <title>Matz Blogs About Waves!</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/hUn8IycH_eQ/matz-blogs-about-waves</link>
          <pubDate>Thu, 07 Feb 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;I am probably way more excited about this than I should be, but I don&amp;#8217;t care. &lt;a href="http://www.rubyist.net/~matz/20080206.html"&gt;Matz has a blog entry about Waves!&lt;/a&gt;&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/matz-blogs-about-waves</feedburner:origLink></item>
        <item>
		  <title>More About Request Lambdas</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/qv8cffl-Hog/more-about-request-mappings</link>
          <pubDate>Wed, 06 Feb 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;I got into a bit of discussion about the concept of request mappings on the mailing list, so I thought I&amp;#8217;d recap that here as my first attempt to look at the nuts and bolts of Waves. Request mappings are akin to routes in Rails or Merb. But there are some profound differences. Request mappings are exactly that &amp;#8211; they map a request to a block of code.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/more-about-request-mappings</feedburner:origLink></item>
        <item>
		  <title>Waves Goes To Beta</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/omF1brqEkhM/announce-0.7.0</link>
          <pubDate>Mon, 04 Feb 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;It&amp;#8217;s taken a bit longer than I&amp;#8217;d hoped, but Waves is finally at beta status, ready to find its way out in the world.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/announce-0.7.0</feedburner:origLink></item>
        <item>
		  <title>Final Alpha Release</title>
          <link>http://feedproxy.google.com/~r/HangTen/~3/IAjO-8JsR1Q/announce-0.6.9</link>
          <pubDate>Thu, 31 Jan 2008 00:00:00 +0000</pubDate>
          <description>
            &lt;p&gt;The last alpha release, last chance for feedback before the public beta release.&lt;/p&gt;
          </description>
        <feedburner:origLink>http://rubywaves.com/announce-0.6.9</feedburner:origLink></item>

    </channel>
</rss>
