<?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 1.2.1 Impression</title>
	<atom:link href="http://push.cx/2007/rails-121-impression/feed" rel="self" type="application/rss+xml" />
	<link>http://push.cx/2007/rails-121-impression</link>
	<description>A traveling geek&#039;s blog on development, games, and the web</description>
	<lastBuildDate>Tue, 10 Apr 2012 23:41:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Mocha - Push cx</title>
		<link>http://push.cx/2007/rails-121-impression/comment-page-1#comment-87709</link>
		<dc:creator>Mocha - Push cx</dc:creator>
		<pubDate>Thu, 17 Apr 2008 01:58:24 +0000</pubDate>
		<guid isPermaLink="false">http://push.cx/2007/rails-121-impression#comment-87709</guid>
		<description>[...] now a big fan of Mocha like I am of Rails. Ruby has a way of allowing coders to write magically polished libraries.   &#171; Simple Ruby [...]</description>
		<content:encoded><![CDATA[<p>[...] now a big fan of Mocha like I am of Rails. Ruby has a way of allowing coders to write magically polished libraries.   &laquo; Simple Ruby [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Human-Readable ActiveResource URLs - Push cx</title>
		<link>http://push.cx/2007/rails-121-impression/comment-page-1#comment-61572</link>
		<dc:creator>Human-Readable ActiveResource URLs - Push cx</dc:creator>
		<pubDate>Tue, 03 Apr 2007 23:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://push.cx/2007/rails-121-impression#comment-61572</guid>
		<description>[...] I&#8217;ve got URLs on the brain this week. I started NearbyGamers using Rails 1.1 with just gamers and tags. I upgraded to Rails 1.2 (and liked it) , and added discussions after I updated to Rails 1.2. I was able to use ActiveResource for Discussions with Posts as a nested resource. I&#8217;m really happy with this code, as it&#8217;s very tidy. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve got URLs on the brain this week. I started NearbyGamers using Rails 1.1 with just gamers and tags. I upgraded to Rails 1.2 (and liked it) , and added discussions after I updated to Rails 1.2. I was able to use ActiveResource for Discussions with Posts as a nested resource. I&#8217;m really happy with this code, as it&#8217;s very tidy. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SOB: Scion Of Backronymics &#187; The Ruby Experience</title>
		<link>http://push.cx/2007/rails-121-impression/comment-page-1#comment-32617</link>
		<dc:creator>SOB: Scion Of Backronymics &#187; The Ruby Experience</dc:creator>
		<pubDate>Thu, 15 Feb 2007 11:39:03 +0000</pubDate>
		<guid isPermaLink="false">http://push.cx/2007/rails-121-impression#comment-32617</guid>
		<description>[...] Well, this first impression of Rails 1.2.1 illustrates something essential to that community and language policy of the Ruby language, something I like about it. Specifically, this bit caught my attention: I’ve mentioned that this is what coding in Rails continually feels like: sometimes it just feels off even though it works and is nicer than other languages, and soon I realize a beautiful Right Way to do it. [...]</description>
		<content:encoded><![CDATA[<p>[...] Well, this first impression of Rails 1.2.1 illustrates something essential to that community and language policy of the Ruby language, something I like about it. Specifically, this bit caught my attention: I’ve mentioned that this is what coding in Rails continually feels like: sometimes it just feels off even though it works and is nicer than other languages, and soon I realize a beautiful Right Way to do it. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Harkins</title>
		<link>http://push.cx/2007/rails-121-impression/comment-page-1#comment-32542</link>
		<dc:creator>Peter Harkins</dc:creator>
		<pubDate>Thu, 15 Feb 2007 05:06:54 +0000</pubDate>
		<guid isPermaLink="false">http://push.cx/2007/rails-121-impression#comment-32542</guid>
		<description>It&#039;s not just that it&#039;s terse that I like it, it&#039;s also because it&#039;s based on the syntax for &lt;a href=&quot;http://www.w3.org/TR/REC-CSS2/selector.html&quot; rel=&quot;nofollow&quot;&gt;CSS selectors&lt;/a&gt;. I looked at it and immediately understood it, it&#039;s less to learn.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not just that it&#8217;s terse that I like it, it&#8217;s also because it&#8217;s based on the syntax for <a href="http://www.w3.org/TR/REC-CSS2/selector.html" rel="nofollow">CSS selectors</a>. I looked at it and immediately understood it, it&#8217;s less to learn.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Silver</title>
		<link>http://push.cx/2007/rails-121-impression/comment-page-1#comment-32539</link>
		<dc:creator>Michael Silver</dc:creator>
		<pubDate>Thu, 15 Feb 2007 04:36:31 +0000</pubDate>
		<guid isPermaLink="false">http://push.cx/2007/rails-121-impression#comment-32539</guid>
		<description>I am new to Ruby and Rails and enjoying learning them.  Perhaps I haven&#039;t been at it long enough, but to me:

assert_select “div#notice &gt; div”, text

is harder to read and understand than the example with assert_tag.  It reminds me of perl, which while a terse language is difficult  to maintain.

Perhaps I just don&#039;t have enough experience under my belt to understand while clarity with wordiness is worse than terse and hard to understand and perhaps it&#039;s just preference.

...Michael...</description>
		<content:encoded><![CDATA[<p>I am new to Ruby and Rails and enjoying learning them.  Perhaps I haven&#8217;t been at it long enough, but to me:</p>
<p>assert_select “div#notice &gt; div”, text</p>
<p>is harder to read and understand than the example with assert_tag.  It reminds me of perl, which while a terse language is difficult  to maintain.</p>
<p>Perhaps I just don&#8217;t have enough experience under my belt to understand while clarity with wordiness is worse than terse and hard to understand and perhaps it&#8217;s just preference.</p>
<p>&#8230;Michael&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

