<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <title>Nimble Code: Extracted Standards</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/23/feed.xml" rel="self" type="application/xml+atom"/>
  <link href="http://www.nimblecode.com/articles/2005/05/02/extracted-standards" rel="alternate" type="text/html"/>
  <updated>2008-11-14T19:26:23-08:00</updated>
  <entry>
    <author>
      <name>harrisj</name>
    </author>
    <id>urn:uuid:420a4ac5f2837123fab29a7accd3d585</id>
    <published>2005-05-02T21:39:00-07:00</published>
    <updated>2008-11-14T19:26:23-08:00</updated>
    <title>Extracted Standards</title>
    <link href="http://www.nimblecode.com/articles/2005/05/02/extracted-standards" rel="alternate" type="text/html"/>
    <category term="web-coding" scheme="http://www.nimblecode.com/articles/category/23" label="Web Coding"/>
    <category term="rails" scheme="http://www.nimblecode.com/articles/tag"/>
    <category term="ruby" scheme="http://www.nimblecode.com/articles/tag"/>
    <category term="soap" scheme="http://www.nimblecode.com/articles/tag"/>
    <content type="html">Still busy, but there is a great article at O'Reilly Radar on how great frameworks are sometimes extracted wholesale from successful applications rather than built from scratch up. That is, it's &lt;a href="http://radar.oreilly.com/archives/2005/04/designing_from.html"&gt;often better to extract the framework from the application&lt;/a&gt;, rather than build the application on top of a framework:

&lt;blockquote&gt;That is, at 37signals, they try to design the usability and function of the application first, and that drives the implementation. And if they can then extract a re-usable framework, all the better. For example, basecamp wasn't built on top of Ruby on Rails. Rather, Ruby on Rails was extracted from basecamp.&lt;/blockquote&gt;

This echoes some of the complaints I was making earlier about the &lt;a href="/blog/?p=22"&gt;unwieldiness of SOAP&lt;/a&gt; for web standards. And it fits in with the philosophy of nimble technologies perfectly. Create a product, solve a need, and make it work great and the frameworks will follow, but complicated frameworks in themselves solve nothing.</content>
  </entry>
</feed>
