<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Time to break it down</title>
	<atom:link href="http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/feed/" rel="self" type="application/rss+xml" />
	<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/</link>
	<description>Hobo - the web app builder for Rails</description>
	<lastBuildDate>Mon, 02 Jan 2012 20:47:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tom</title>
		<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/comment-page-1/#comment-19511</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 28 Dec 2007 10:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/#comment-19511</guid>
		<description>&lt;p&gt;Jon - yes we have taken a look at merb. It does seem to offer some improvements over Rails, and the team seem to have a stronger commitment to a pluggable architecture, which is great for a project like Hobo.&lt;/p&gt;

&lt;p&gt;The fact is though, Rails has the traction. There are many factors to consider that are not technical. I&#039;m a strong believer in the idea that the vale of any software infrastructure is directly proportional to how widely it is used.&lt;/p&gt;

&lt;p&gt;So for now we&#039;ll definitely be sticking with Rails, but keeping a watchful eye on merb.&lt;/p&gt;

&lt;p&gt;Some of the Hobo components, particularly DRYML, could conceivably be made compatible with both. That would be very cool :-)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Jon &#8211; yes we have taken a look at merb. It does seem to offer some improvements over Rails, and the team seem to have a stronger commitment to a pluggable architecture, which is great for a project like Hobo.</p>
<p>The fact is though, Rails has the traction. There are many factors to consider that are not technical. I&#8217;m a strong believer in the idea that the vale of any software infrastructure is directly proportional to how widely it is used.</p>
<p>So for now we&#8217;ll definitely be sticking with Rails, but keeping a watchful eye on merb.</p>
<p>Some of the Hobo components, particularly DRYML, could conceivably be made compatible with both. That would be very cool :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/comment-page-1/#comment-19443</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Thu, 27 Dec 2007 14:41:35 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/#comment-19443</guid>
		<description>&lt;p&gt;With you guys breaking up the pieces of your app, have you thought about using something like merb (http://www.merbivore.com/) in stead of rails? It looks like both teams are having a similar approach: have a strong default set of tools but make it plugable in case those tools don&#039;t suit everyone.&lt;/p&gt;

&lt;p&gt;Personally, I&#039;d think the combination of merb with datamapper, validatable, rspec and DRYML would be pretty strong.&lt;/p&gt;

&lt;p&gt;Just my opinion. Good luck with the breakdown of the components. I can&#039;t wait for the DRYML gem/plugin. Keep up the terrific work.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>With you guys breaking up the pieces of your app, have you thought about using something like merb (<a href="http://www.merbivore.com/" rel="nofollow">http://www.merbivore.com/</a>) in stead of rails? It looks like both teams are having a similar approach: have a strong default set of tools but make it plugable in case those tools don&#8217;t suit everyone.</p>
<p>Personally, I&#8217;d think the combination of merb with datamapper, validatable, rspec and DRYML would be pretty strong.</p>
<p>Just my opinion. Good luck with the breakdown of the components. I can&#8217;t wait for the DRYML gem/plugin. Keep up the terrific work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/comment-page-1/#comment-15873</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 20 Nov 2007 10:06:20 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/#comment-15873</guid>
		<description>&lt;p&gt;Andy - there is one (part of rthe Hobo Trac) at dev.hobocentral.net&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Andy &#8211; there is one (part of rthe Hobo Trac) at dev.hobocentral.net</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Finn Higgins</title>
		<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/comment-page-1/#comment-15808</link>
		<dc:creator>Finn Higgins</dc:creator>
		<pubDate>Mon, 19 Nov 2007 21:33:52 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/#comment-15808</guid>
		<description>&lt;p&gt;Wow. Boy do I feel special!&lt;/p&gt;

&lt;p&gt;That&#039;s incredibly good news, and really all I could possibly have hoped for in terms of keeping track of Hobo as a dependency.  You guys are utter champions.&lt;/p&gt;

&lt;p&gt;At the moment I have a few projects that are specifically Rails-only affairs because the model structure isn&#039;t too well-suited to Hobo&#039;s assumptions about data.  But being able to move the views to DRYML would really make my day.&lt;/p&gt;

&lt;p&gt;I&#039;m a very happy man.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Wow. Boy do I feel special!</p>
<p>That&#8217;s incredibly good news, and really all I could possibly have hoped for in terms of keeping track of Hobo as a dependency.  You guys are utter champions.</p>
<p>At the moment I have a few projects that are specifically Rails-only affairs because the model structure isn&#8217;t too well-suited to Hobo&#8217;s assumptions about data.  But being able to move the views to DRYML would really make my day.</p>
<p>I&#8217;m a very happy man.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/comment-page-1/#comment-15359</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 16 Nov 2007 12:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/#comment-15359</guid>
		<description>&lt;p&gt;How about a hobo wiki, to document features and host tutorials?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>How about a hobo wiki, to document features and host tutorials?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bronson</title>
		<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/comment-page-1/#comment-15273</link>
		<dc:creator>bronson</dc:creator>
		<pubDate>Thu, 15 Nov 2007 19:23:12 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/#comment-15273</guid>
		<description>&lt;p&gt;I should mention that I don&#039;t bill for Hobo upgrade breakage.  I chose Hobo, I get to deal with the consequences myself.  :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I should mention that I don&#8217;t bill for Hobo upgrade breakage.  I chose Hobo, I get to deal with the consequences myself.  :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bronson</title>
		<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/comment-page-1/#comment-15271</link>
		<dc:creator>bronson</dc:creator>
		<pubDate>Thu, 15 Nov 2007 19:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/#comment-15271</guid>
		<description>&lt;p&gt;I started playing with documentation a while ago.  Here&#039;s an attempt to get NaturalDocs to work: http://u32.net/tagdoc-noframes  WARNING: that&#039;s intended to see if NaturalDocs would work for Hobo; the actual documentation there pretty much sucks.&lt;/p&gt;

&lt;p&gt;Verdict: NaturalDocs is crufty.  I&#039;ll try to get rdoc to work next, but it&#039;s going to take a fair bit of effort and I don&#039;t know when I&#039;m going to get the time.  :-/&lt;/p&gt;

&lt;p&gt;Kwahu, I&#039;m not sure fighting to get people to use Hobo is a productive thing to do right now.  :)  Personally, I think Hobo is the most exciting thing to happen in all of Rails history but it&#039;s still awfully unstable.  And I&#039;m glad it is -- it&#039;s improving incredibly fast yet accruing very little cruft.&lt;/p&gt;

&lt;p&gt;Still, because of that, I wouldn&#039;t consider bringing Hobo into the enterprise right now.  (that said, I actually am using it in the enterprise myself, but they don&#039;t know yet and by the time they care Hobo will be stable ;).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I started playing with documentation a while ago.  Here&#8217;s an attempt to get NaturalDocs to work: <a href="http://u32.net/tagdoc-noframes" rel="nofollow">http://u32.net/tagdoc-noframes</a>  WARNING: that&#8217;s intended to see if NaturalDocs would work for Hobo; the actual documentation there pretty much sucks.</p>
<p>Verdict: NaturalDocs is crufty.  I&#8217;ll try to get rdoc to work next, but it&#8217;s going to take a fair bit of effort and I don&#8217;t know when I&#8217;m going to get the time.  :-/</p>
<p>Kwahu, I&#8217;m not sure fighting to get people to use Hobo is a productive thing to do right now.  :)  Personally, I think Hobo is the most exciting thing to happen in all of Rails history but it&#8217;s still awfully unstable.  And I&#8217;m glad it is &#8212; it&#8217;s improving incredibly fast yet accruing very little cruft.</p>
<p>Still, because of that, I wouldn&#8217;t consider bringing Hobo into the enterprise right now.  (that said, I actually am using it in the enterprise myself, but they don&#8217;t know yet and by the time they care Hobo will be stable ;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen</title>
		<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/comment-page-1/#comment-15259</link>
		<dc:creator>Owen</dc:creator>
		<pubDate>Thu, 15 Nov 2007 17:45:18 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/#comment-15259</guid>
		<description>&lt;p&gt;I think breaking the releases into digestible chunks makes great sense.  What do you think the order will be?  That would help us for planning purposes.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I think breaking the releases into digestible chunks makes great sense.  What do you think the order will be?  That would help us for planning purposes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ylon</title>
		<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/comment-page-1/#comment-15257</link>
		<dc:creator>ylon</dc:creator>
		<pubDate>Thu, 15 Nov 2007 17:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/#comment-15257</guid>
		<description>&lt;p&gt;Well, perhaps we should take the following approach?  Obviously Tom &amp; company are going to be doing that which is outlined, however perhaps if we did start with some sort of master list as Kwahu is saying and allow community driven documentation to help Tom and James out along the way so folks could break out and write a little bit about each piece that they discover or things which are explained in IRC, etc..  Just brainstorming, but trying to make things easier for the core developers.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Well, perhaps we should take the following approach?  Obviously Tom &amp; company are going to be doing that which is outlined, however perhaps if we did start with some sort of master list as Kwahu is saying and allow community driven documentation to help Tom and James out along the way so folks could break out and write a little bit about each piece that they discover or things which are explained in IRC, etc..  Just brainstorming, but trying to make things easier for the core developers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kwahu</title>
		<link>http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/comment-page-1/#comment-15215</link>
		<dc:creator>Kwahu</dc:creator>
		<pubDate>Thu, 15 Nov 2007 11:54:40 +0000</pubDate>
		<guid isPermaLink="false">http://hobocentral.net/blog/2007/11/14/time-to-break-it-down/#comment-15215</guid>
		<description>&lt;p&gt;The lack of documentation is a biggest problem in my company. I&#039;m one of 3 ppl that where using HOBO right now and if not my faith in HOBO we would drop using HOBO a long time ago. I have to fight with the rest of the team every day. A least a list of avilable features (even without explanation) would help a lot!!!&lt;/p&gt;

&lt;p&gt;Sometimes I just don&#039;t knew that I can do a certain thing. If I knew about sth I have a 100% more chance that I will use it lets say by asking other ppl how to use it ;)&lt;/p&gt;

&lt;p&gt;Please publicate a list a least ;)&lt;/p&gt;

&lt;p&gt;Hugs to all HOBO Team and the HOBO Community !&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The lack of documentation is a biggest problem in my company. I&#8217;m one of 3 ppl that where using HOBO right now and if not my faith in HOBO we would drop using HOBO a long time ago. I have to fight with the rest of the team every day. A least a list of avilable features (even without explanation) would help a lot!!!</p>
<p>Sometimes I just don&#8217;t knew that I can do a certain thing. If I knew about sth I have a 100% more chance that I will use it lets say by asking other ppl how to use it ;)</p>
<p>Please publicate a list a least ;)</p>
<p>Hugs to all HOBO Team and the HOBO Community !</p>
]]></content:encoded>
	</item>
</channel>
</rss>

