<?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: Elements of Ruby Style</title>
	<atom:link href="http://pathfindersoftware.com/2008/10/elements-of-ruby-style/feed/" rel="self" type="application/rss+xml" />
	<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/</link>
	<description>The Fastest Way to Launch Successful Software</description>
	<lastBuildDate>Thu, 19 Jan 2012 16:36:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: CSS Coding Standards &#124; Samurai Coder</title>
		<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/#comment-8903</link>
		<dc:creator>CSS Coding Standards &#124; Samurai Coder</dc:creator>
		<pubDate>Fri, 17 Jul 2009 15:26:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1205#comment-8903</guid>
		<description>[...] considered a constant, not a variable.) But still there&#8217;s wide open room for its style. Noel Rappin wrote a style guide,  which I found quite inspiring. Any similar efforts on CSS? Can any well-known CSS maven have a [...]</description>
		<content:encoded><![CDATA[<p>[...] considered a constant, not a variable.) But still there&#8217;s wide open room for its style. Noel Rappin wrote a style guide,  which I found quite inspiring. Any similar efforts on CSS? Can any well-known CSS maven have a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kenn</title>
		<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/#comment-8902</link>
		<dc:creator>Kenn</dc:creator>
		<pubDate>Sat, 20 Dec 2008 01:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1205#comment-8902</guid>
		<description>Of course the beauty of using tabs for indentation is that your editor will display them at whatever width you prefer, while not imposing your own width preferences on others.

For the record, I do single-tab indent and display them with a width of four characters. Everyone wins.</description>
		<content:encoded><![CDATA[<p>Of course the beauty of using tabs for indentation is that your editor will display them at whatever width you prefer, while not imposing your own width preferences on others.</p>
<p>For the record, I do single-tab indent and display them with a width of four characters. Everyone wins.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry</title>
		<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/#comment-8901</link>
		<dc:creator>Barry</dc:creator>
		<pubDate>Sat, 15 Nov 2008 04:38:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1205#comment-8901</guid>
		<description>@Harry,

Maybe even
return if x.nil?</description>
		<content:encoded><![CDATA[<p>@Harry,</p>
<p>Maybe even<br />
return if x.nil?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Juixe TechKnow &#187; The Rubyist: October Edition</title>
		<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/#comment-8900</link>
		<dc:creator>Juixe TechKnow &#187; The Rubyist: October Edition</dc:creator>
		<pubDate>Fri, 14 Nov 2008 07:16:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1205#comment-8900</guid>
		<description>[...] Elements of Ruby Style [...]</description>
		<content:encoded><![CDATA[<p>[...] Elements of Ruby Style [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: เร็วส์ หกสิบหก » นั่งเทียนเขียนข่าว#22</title>
		<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/#comment-8899</link>
		<dc:creator>เร็วส์ หกสิบหก » นั่งเทียนเขียนข่าว#22</dc:creator>
		<pubDate>Sun, 02 Nov 2008 17:18:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1205#comment-8899</guid>
		<description>[...] Elements of Ruby Style - Ruby Stylista - [...]</description>
		<content:encoded><![CDATA[<p>[...] Elements of Ruby Style &#8211; Ruby Stylista &#8211; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sho</title>
		<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/#comment-8898</link>
		<dc:creator>Sho</dc:creator>
		<pubDate>Fri, 31 Oct 2008 07:44:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1205#comment-8898</guid>
		<description>@gw:

Most Ruby users that I know care deeply about the &quot;look and feel&quot; of the language they use - that&#039;s the whole reason they love Ruby so much. Efforts to come up with the &quot;best practise&quot; for writing clear, understandable, good looking code are not elitism or an effort to become &quot;cool kids&quot;. It&#039;s more an effort to arrive at some kind of ideal standard form, by people who care deeply about style and function.

And more than 2 spaces is ridiculous. Maybe 4 spaces is necessary for Java, a much more verbose language, else the indentation gets lost in a sea of code .. but Ruby is far more concise. 2 spaces is fine in well written code.

Also, I disagree that Ruby is becoming less friendly. There&#039;s a few new corporate wannabe wankers around, sure, but you get that anywhere. The ruby people I know are friendly as anything. Calm down, cheer up and have a little more faith in people.</description>
		<content:encoded><![CDATA[<p>@gw:</p>
<p>Most Ruby users that I know care deeply about the &#8220;look and feel&#8221; of the language they use &#8211; that&#8217;s the whole reason they love Ruby so much. Efforts to come up with the &#8220;best practise&#8221; for writing clear, understandable, good looking code are not elitism or an effort to become &#8220;cool kids&#8221;. It&#8217;s more an effort to arrive at some kind of ideal standard form, by people who care deeply about style and function.</p>
<p>And more than 2 spaces is ridiculous. Maybe 4 spaces is necessary for Java, a much more verbose language, else the indentation gets lost in a sea of code .. but Ruby is far more concise. 2 spaces is fine in well written code.</p>
<p>Also, I disagree that Ruby is becoming less friendly. There&#8217;s a few new corporate wannabe wankers around, sure, but you get that anywhere. The ruby people I know are friendly as anything. Calm down, cheer up and have a little more faith in people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gw</title>
		<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/#comment-8897</link>
		<dc:creator>gw</dc:creator>
		<pubDate>Wed, 29 Oct 2008 07:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1205#comment-8897</guid>
		<description>2 spaces? no way. 80 char limit? no way. Standard if structure is much clearer than the proposed alternatives. Avoid ternary? Pfft, don&#039;t think so--especially for short lines. Leave out last return? Don&#039;t care for that at ll. Code should be explicit wherever possible. return x is instantly recognizable as to purpose and function. Stringing things together goes &quot;overboard&quot; very quickly IMO. smaller steps on more lines is usually easier to read than one-liner magic.

I like Ruby, but I don&#039;t care for a lot of the style and idioms that are completely counter to most other languages and practices just so the people using them can be the &quot;kewl kids.&quot; Worse is the flogging certain community folks give when their arbitrary favorite style isn&#039;t followed. It feels a lot like royal manners--designed to make a small group feel elite because they follow some arbitrary rules. It&#039;s just style snobbery and doesn&#039;t fit within the usually friendly atmosphere of teh Ruby community (slowly being eroded as elitism spreads).</description>
		<content:encoded><![CDATA[<p>2 spaces? no way. 80 char limit? no way. Standard if structure is much clearer than the proposed alternatives. Avoid ternary? Pfft, don&#8217;t think so&#8211;especially for short lines. Leave out last return? Don&#8217;t care for that at ll. Code should be explicit wherever possible. return x is instantly recognizable as to purpose and function. Stringing things together goes &#8220;overboard&#8221; very quickly IMO. smaller steps on more lines is usually easier to read than one-liner magic.</p>
<p>I like Ruby, but I don&#8217;t care for a lot of the style and idioms that are completely counter to most other languages and practices just so the people using them can be the &#8220;kewl kids.&#8221; Worse is the flogging certain community folks give when their arbitrary favorite style isn&#8217;t followed. It feels a lot like royal manners&#8211;designed to make a small group feel elite because they follow some arbitrary rules. It&#8217;s just style snobbery and doesn&#8217;t fit within the usually friendly atmosphere of teh Ruby community (slowly being eroded as elitism spreads).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruby Style Guides and Tools: How to Write Good Looking Ruby : WebNetiques</title>
		<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/#comment-8896</link>
		<dc:creator>Ruby Style Guides and Tools: How to Write Good Looking Ruby : WebNetiques</dc:creator>
		<pubDate>Tue, 28 Oct 2008 09:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1205#comment-8896</guid>
		<description>[...] week, Noel Rappin of Pathfinder Development wrote Elements of Ruby Style - an attempt at producing a Ruby &#8220;style guide.&#8221; After some initial feedback to this, [...]</description>
		<content:encoded><![CDATA[<p>[...] week, Noel Rappin of Pathfinder Development wrote Elements of Ruby Style &#8211; an attempt at producing a Ruby &#8220;style guide.&#8221; After some initial feedback to this, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nona</title>
		<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/#comment-8895</link>
		<dc:creator>Nona</dc:creator>
		<pubDate>Tue, 28 Oct 2008 02:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1205#comment-8895</guid>
		<description>Please divorce your current editor if it hides code on long lines.  Any programmer&#039;s editor will do the correct thing and wrap.</description>
		<content:encoded><![CDATA[<p>Please divorce your current editor if it hides code on long lines.  Any programmer&#8217;s editor will do the correct thing and wrap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vBharat.com &#187; Pathfinder Development » Elements of Ruby Style</title>
		<link>http://pathfindersoftware.com/2008/10/elements-of-ruby-style/#comment-8894</link>
		<dc:creator>vBharat.com &#187; Pathfinder Development » Elements of Ruby Style</dc:creator>
		<pubDate>Mon, 27 Oct 2008 23:20:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=1205#comment-8894</guid>
		<description>&lt;strong&gt;From vBharat.com &#187; Pathfinder Development » Elements of Ruby Style...&lt;/strong&gt;

Here are some thoughts on good Ruby &amp; Rails style -- I&#039;m mostly focusing on Ruby-specific guidelines here. This is somewhat closer to a brain dump than a fully-baked style guide, so it&#039;s something I intend to come back to, especially after hearing ev...</description>
		<content:encoded><![CDATA[<p><strong>From vBharat.com &#187; Pathfinder Development » Elements of Ruby Style&#8230;</strong></p>
<p>Here are some thoughts on good Ruby &amp; Rails style &#8212; I&#8217;m mostly focusing on Ruby-specific guidelines here. This is somewhat closer to a brain dump than a fully-baked style guide, so it&#8217;s something I intend to come back to, especially after hearing ev&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic (User agent is rejected)
Page Caching using memcached (User agent is rejected)

Served from: pathfindersoftware.com @ 2012-02-10 00:47:18 -->
