<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Need a bike in Paris?</title>
	<link>http://chilco.textdrive.com/~dmahugh/2008/04/24/need-a-bike-in-paris/</link>
	<description></description>
	<pubDate>Mon, 01 Dec 2008 20:02:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Doug</title>
		<link>http://chilco.textdrive.com/~dmahugh/2008/04/24/need-a-bike-in-paris/#comment-39266</link>
		<author>Doug</author>
		<pubDate>Mon, 28 Apr 2008 21:46:52 +0000</pubDate>
		<guid>http://chilco.textdrive.com/~dmahugh/2008/04/24/need-a-bike-in-paris/#comment-39266</guid>
		<description>Hey, for arguing with your Python friends, you might want to read this very details comparison of Ruby and Python: http://blog.ianbicking.org/ruby-python-power.html</description>
		<content:encoded><![CDATA[<p>Hey, for arguing with your Python friends, you might want to read this very details comparison of Ruby and Python: <a href="http://blog.ianbicking.org/ruby-python-power.html" rel="nofollow">http://blog.ianbicking.org/ruby-python-power.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://chilco.textdrive.com/~dmahugh/2008/04/24/need-a-bike-in-paris/#comment-39265</link>
		<author>Tom</author>
		<pubDate>Mon, 28 Apr 2008 20:33:39 +0000</pubDate>
		<guid>http://chilco.textdrive.com/~dmahugh/2008/04/24/need-a-bike-in-paris/#comment-39265</guid>
		<description>Cool. I can't dig into it right now, but maybe later this week. I'd love to be able to argue with all my Python friends (who are a bit too rabid for my taste about a lot of things). 

Hey, just saw &lt;a href="http://ejohn.org/blog/ruby-vm-in-javascript/" rel="nofollow"&gt;this&lt;/a&gt; link on Slashdot today. Might be fun to play with, too.</description>
		<content:encoded><![CDATA[<p>Cool. I can&#8217;t dig into it right now, but maybe later this week. I&#8217;d love to be able to argue with all my Python friends (who are a bit too rabid for my taste about a lot of things). </p>
<p>Hey, just saw <a href="http://ejohn.org/blog/ruby-vm-in-javascript/" rel="nofollow">this</a> link on Slashdot today. Might be fun to play with, too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug</title>
		<link>http://chilco.textdrive.com/~dmahugh/2008/04/24/need-a-bike-in-paris/#comment-39246</link>
		<author>Doug</author>
		<pubDate>Mon, 28 Apr 2008 05:16:44 +0000</pubDate>
		<guid>http://chilco.textdrive.com/~dmahugh/2008/04/24/need-a-bike-in-paris/#comment-39246</guid>
		<description>Hmm.  Intuitive.  I'd say that Ruby on Rails is intuitive if you're thinking in terms of MVC (model-view-controller, a design pattern first popularized in Smalltalk environments of the early 80s).  MVC is one of those things that makes great sense, and I've done things that borrow from it at various times, but RoR all but enforces it: you absolutely positively must think in those terms.  If you do, it's a super-productive environment.

Ruby is a pretty elegant and consistent language, a combination of Perl-style scripting (think productivity) and Smalltak-style object orientation (think flexibility -- "everything's an object").  And RoR takes full advantage of Ruby, leading to valid code that includes expressions like &lt;b&gt;30.months + 15.minutes&lt;/b&gt; (a perfectly valid expression in a Rails app).

Here's the best brief tutorial I've seen: http://fairleads.blogspot.com/2007/12/rails-20-and-scaffolding-step-by-step.html

I'd recommend installing Instant Rails (&lt;a href="http://instantrails.rubyforge.org/wiki/wiki.pl" rel="nofollow"&gt;http://instantrails.rubyforge.org/wiki/wiki.pl&lt;/a&gt;) and then do Sean's tutorial at the link above.  In about 15 minutes you'll have a hands-on opinion.   And besides, I need somebody to help me stagger through the learning curve.  Safety in numbers, you know.</description>
		<content:encoded><![CDATA[<p>Hmm.  Intuitive.  I&#8217;d say that Ruby on Rails is intuitive if you&#8217;re thinking in terms of MVC (model-view-controller, a design pattern first popularized in Smalltalk environments of the early 80s).  MVC is one of those things that makes great sense, and I&#8217;ve done things that borrow from it at various times, but RoR all but enforces it: you absolutely positively must think in those terms.  If you do, it&#8217;s a super-productive environment.</p>
<p>Ruby is a pretty elegant and consistent language, a combination of Perl-style scripting (think productivity) and Smalltak-style object orientation (think flexibility &#8212; &#8220;everything&#8217;s an object&#8221;).  And RoR takes full advantage of Ruby, leading to valid code that includes expressions like <b>30.months + 15.minutes</b> (a perfectly valid expression in a Rails app).</p>
<p>Here&#8217;s the best brief tutorial I&#8217;ve seen: <a href="http://fairleads.blogspot.com/2007/12/rails-20-and-scaffolding-step-by-step.html" rel="nofollow">http://fairleads.blogspot.com/2007/12/rails-20-and-scaffolding-step-by-step.html</a></p>
<p>I&#8217;d recommend installing Instant Rails (<a href="http://instantrails.rubyforge.org/wiki/wiki.pl" rel="nofollow">http://instantrails.rubyforge.org/wiki/wiki.pl</a>) and then do Sean&#8217;s tutorial at the link above.  In about 15 minutes you&#8217;ll have a hands-on opinion.   And besides, I need somebody to help me stagger through the learning curve.  Safety in numbers, you know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://chilco.textdrive.com/~dmahugh/2008/04/24/need-a-bike-in-paris/#comment-39230</link>
		<author>Tom</author>
		<pubDate>Sun, 27 Apr 2008 20:59:34 +0000</pubDate>
		<guid>http://chilco.textdrive.com/~dmahugh/2008/04/24/need-a-bike-in-paris/#comment-39230</guid>
		<description>Don't know a lot about Ruby on Rails, but I've done some stuff in Python. The two are, as near as I can tell, compared in much the same way Windows and OS X are compared in the geek community. You know, rabidly and with little room for the other approach. 

I know Python is very cool, and can only assume that Ruby on Rails is, too. Where did you do your reading about it? Or did you jump into it some other way? 

One of the easiest languages I ever wrote in was Object Rexx -- Rexx was originally a scripting language for the AS/400, and Object Rexx was an offshoot of that. Very conversational. It had some idiosyncrasies (its logical operators were a little funky, so going back and forth from PHP or Python to Rexx took a little mental gymnastics), but neat nonethless. 

Another neat one I just learned about is &lt;a href="http://www.duke.edu/~srg3/IFprogramming/inform.html" rel="nofollow"&gt;Inform&lt;/a&gt; -- it's a result of reverse engineering the old Infocom text games (Zork, Hitchhikers Guide to the Galaxy, etc.). A typical snippet of code is: 

&lt;blockquote&gt;The Deathbot Assembly Line is a room. "Here is the heart of the whole operation, where your opponents are assembled fresh from scrap metal and bits of old car." The dangerous robot is a thing in the Assembly Line. "One dangerous robot looks ready to take you on!" A robotic head, a drill arm, a needle arm, a crushing leg and a kicking leg are parts of the dangerous robot. &lt;/blockquote&gt;

(I hope that blockquote tag works -- if not, please don't hesitate to edit.) 

But I digress. Did you find Ruby on Rails to be pretty intuitive? I've heard it has a steeper learning curve than Python, but it seems to me that I see them each about the same amount in job ads and curricula.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t know a lot about Ruby on Rails, but I&#8217;ve done some stuff in Python. The two are, as near as I can tell, compared in much the same way Windows and OS X are compared in the geek community. You know, rabidly and with little room for the other approach. </p>
<p>I know Python is very cool, and can only assume that Ruby on Rails is, too. Where did you do your reading about it? Or did you jump into it some other way? </p>
<p>One of the easiest languages I ever wrote in was Object Rexx &#8212; Rexx was originally a scripting language for the AS/400, and Object Rexx was an offshoot of that. Very conversational. It had some idiosyncrasies (its logical operators were a little funky, so going back and forth from PHP or Python to Rexx took a little mental gymnastics), but neat nonethless. </p>
<p>Another neat one I just learned about is <a href="http://www.duke.edu/~srg3/IFprogramming/inform.html" rel="nofollow">Inform</a> &#8212; it&#8217;s a result of reverse engineering the old Infocom text games (Zork, Hitchhikers Guide to the Galaxy, etc.). A typical snippet of code is: </p>
<blockquote><p>The Deathbot Assembly Line is a room. &#8220;Here is the heart of the whole operation, where your opponents are assembled fresh from scrap metal and bits of old car.&#8221; The dangerous robot is a thing in the Assembly Line. &#8220;One dangerous robot looks ready to take you on!&#8221; A robotic head, a drill arm, a needle arm, a crushing leg and a kicking leg are parts of the dangerous robot. </p></blockquote>
<p>(I hope that blockquote tag works &#8212; if not, please don&#8217;t hesitate to edit.) </p>
<p>But I digress. Did you find Ruby on Rails to be pretty intuitive? I&#8217;ve heard it has a steeper learning curve than Python, but it seems to me that I see them each about the same amount in job ads and curricula.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
