<?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: Rails Edge Architecture</title>
	<atom:link href="http://yehudakatz.com/2009/06/11/rails-edge-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/</link>
	<description>Random Geek-Related Thoughts</description>
	<lastBuildDate>Sat, 20 Apr 2013 07:23:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nelson</title>
		<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/comment-page-1/#comment-21337</link>
		<dc:creator>Nelson</dc:creator>
		<pubDate>Thu, 07 Oct 2010 22:59:53 +0000</pubDate>
		<guid isPermaLink="false">http://yehudakatz.com/?p=257#comment-21337</guid>
		<description><![CDATA[Hey Yehuda,


first of all i would like to thank you, for your great work and your valuable contributions for the rails project.
Now to your, i know, older post:
i look for a graphical documentation of the rails architecture, because i agree with your argument, that it is too difficult the read the core by it self without a explanation. A good diagramm or flow-chart would be great, it creates a smoother access in the project, even for the academic world ;) otherwise they don&#039;t believe it

Is there something in work?

Cheers]]></description>
		<content:encoded><![CDATA[<p>Hey Yehuda,</p>
<p>first of all i would like to thank you, for your great work and your valuable contributions for the rails project.<br />
Now to your, i know, older post:<br />
i look for a graphical documentation of the rails architecture, because i agree with your argument, that it is too difficult the read the core by it self without a explanation. A good diagramm or flow-chart would be great, it creates a smoother access in the project, even for the academic world ;) otherwise they don&#8217;t believe it</p>
<p>Is there something in work?</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Thomson</title>
		<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/comment-page-1/#comment-21165</link>
		<dc:creator>Bill Thomson</dc:creator>
		<pubDate>Sat, 02 Oct 2010 03:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://yehudakatz.com/?p=257#comment-21165</guid>
		<description><![CDATA[You actually did a good job making it sound not too complex, Yehuda. I&#039;m curious where is the best place to get solid documentation on Rails 3? I know of a few resources, but would certainly love to have more. Cheers.]]></description>
		<content:encoded><![CDATA[<p>You actually did a good job making it sound not too complex, Yehuda. I&#8217;m curious where is the best place to get solid documentation on Rails 3? I know of a few resources, but would certainly love to have more. Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michal</title>
		<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/comment-page-1/#comment-16605</link>
		<dc:creator>Michal</dc:creator>
		<pubDate>Fri, 19 Jun 2009 12:21:37 +0000</pubDate>
		<guid isPermaLink="false">http://yehudakatz.com/?p=257#comment-16605</guid>
		<description><![CDATA[Thanks for your hard work!
You mentioned graphics outlining internal design of rails. Is it published anywhere?]]></description>
		<content:encoded><![CDATA[<p>Thanks for your hard work!<br />
You mentioned graphics outlining internal design of rails. Is it published anywhere?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Burrows</title>
		<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/comment-page-1/#comment-16570</link>
		<dc:creator>Mike Burrows</dc:creator>
		<pubDate>Sat, 13 Jun 2009 09:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://yehudakatz.com/?p=257#comment-16570</guid>
		<description><![CDATA[Quick q: will Rails 3 identify to the controller the route object that matched the request?  This could be really useful for automatically generating link headers etc.]]></description>
		<content:encoded><![CDATA[<p>Quick q: will Rails 3 identify to the controller the route object that matched the request?  This could be really useful for automatically generating link headers etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Moreno</title>
		<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/comment-page-1/#comment-16568</link>
		<dc:creator>Greg Moreno</dc:creator>
		<pubDate>Fri, 12 Jun 2009 19:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://yehudakatz.com/?p=257#comment-16568</guid>
		<description><![CDATA[Thanks for the post, Yehuda. I can&#039;t wait to see the diagrams and docs on the internals of Rails.

After years of existence, other framework developers would not dare do massive refactorings to get things right. What you&#039;re doing shows a strong commitment to the success of Rails. The Rails community owes you guys big time :)]]></description>
		<content:encoded><![CDATA[<p>Thanks for the post, Yehuda. I can&#8217;t wait to see the diagrams and docs on the internals of Rails.</p>
<p>After years of existence, other framework developers would not dare do massive refactorings to get things right. What you&#8217;re doing shows a strong commitment to the success of Rails. The Rails community owes you guys big time :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Smock</title>
		<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/comment-page-1/#comment-16567</link>
		<dc:creator>Jon Smock</dc:creator>
		<pubDate>Fri, 12 Jun 2009 17:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://yehudakatz.com/?p=257#comment-16567</guid>
		<description><![CDATA[Putting the Rails2Compatibility stuff in a separate module was genius.  I like that a lot.

@DarkTatka - Good point on the testing.  I need a good reminder like this every now and again... :-D]]></description>
		<content:encoded><![CDATA[<p>Putting the Rails2Compatibility stuff in a separate module was genius.  I like that a lot.</p>
<p>@DarkTatka &#8211; Good point on the testing.  I need a good reminder like this every now and again&#8230; :-D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DarkTatka</title>
		<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/comment-page-1/#comment-16566</link>
		<dc:creator>DarkTatka</dc:creator>
		<pubDate>Fri, 12 Jun 2009 13:50:03 +0000</pubDate>
		<guid isPermaLink="false">http://yehudakatz.com/?p=257#comment-16566</guid>
		<description><![CDATA[This kind of refactoring in such relatively short time always reminds me how much solid test base can do. Big thank you for making it easier to understand &quot;what the hell is going on in there&quot;.]]></description>
		<content:encoded><![CDATA[<p>This kind of refactoring in such relatively short time always reminds me how much solid test base can do. Big thank you for making it easier to understand &#8220;what the hell is going on in there&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RaghuonRails</title>
		<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/comment-page-1/#comment-16563</link>
		<dc:creator>RaghuonRails</dc:creator>
		<pubDate>Fri, 12 Jun 2009 05:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://yehudakatz.com/?p=257#comment-16563</guid>
		<description><![CDATA[Thanks for the great post on the architecture specification on Rails 3 !!]]></description>
		<content:encoded><![CDATA[<p>Thanks for the great post on the architecture specification on Rails 3 !!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabe da Silveira</title>
		<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/comment-page-1/#comment-16561</link>
		<dc:creator>Gabe da Silveira</dc:creator>
		<pubDate>Thu, 11 Jun 2009 20:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://yehudakatz.com/?p=257#comment-16561</guid>
		<description><![CDATA[You and the rest of the team are doing great work on this yehuda.  I&#039;m a bit more familiar with AR internals than AP, but your description sounds really good.  I got a bit of the taste of the overgrown and tightly coupled abstractions as they existed when I created the Rails-Multisite plugin to allow productization of an by means of multiple views directories.  Looking forward to upgrading the plugin to Rails 3.0 and checking out the tasty goodness.

Also, just in general it&#039;s exciting that all these years later Rails is still able to do these kinds of massive refactorings.]]></description>
		<content:encoded><![CDATA[<p>You and the rest of the team are doing great work on this yehuda.  I&#8217;m a bit more familiar with AR internals than AP, but your description sounds really good.  I got a bit of the taste of the overgrown and tightly coupled abstractions as they existed when I created the Rails-Multisite plugin to allow productization of an by means of multiple views directories.  Looking forward to upgrading the plugin to Rails 3.0 and checking out the tasty goodness.</p>
<p>Also, just in general it&#8217;s exciting that all these years later Rails is still able to do these kinds of massive refactorings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wycats</title>
		<link>http://yehudakatz.com/2009/06/11/rails-edge-architecture/comment-page-1/#comment-16558</link>
		<dc:creator>wycats</dc:creator>
		<pubDate>Thu, 11 Jun 2009 14:14:15 +0000</pubDate>
		<guid isPermaLink="false">http://yehudakatz.com/?p=257#comment-16558</guid>
		<description><![CDATA[That&#039;s the idea. Right now (on edge), it&#039;s very easy to build your own controller with just the features you need (and then inherit ApplicationController from that). The goal is to make the compatibility module optional.]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s the idea. Right now (on edge), it&#8217;s very easy to build your own controller with just the features you need (and then inherit ApplicationController from that). The goal is to make the compatibility module optional.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
