From: Robert Klemme <shortcutter@...>
Date: 2009-10-07T06:55:04+09:00
Subject: Re: Ruby for the wrong reason

On 10/06/2009 08:16 AM, 7stud -- wrote:
> flebber wrote:
>> Secondly I found capturing the date input from a console in python to
>> be a little long winded, below is the script I wrote in python would
>> this be significantly easier in Ruby.
>>
> 
> No.  I think in ruby the code would be almost exactly the same--except 
> it's significantly harder to figure out in ruby because there is no 
> documentation about the format specifiers you can use with strftime() 
> and strptime().  Amazing, huh?

It's not very good to find but what about this?

http://ruby-doc.org/core-1.8.7/classes/Time.html#M000139

>> Which version of Ruby should I use 1.8.6, 1.9.1 or a preview version
>> of 1.9.2?
> 
> ruby and python are in the same state of evolution right now--both are 
> in the midst of a major version change.  In both cases, the newer 
> versions won't have as many libraries available to them because most 
> libraries have not yet been rewritten to accommodate the latest version. 
> So the choice is: go with ruby 1.8.6 and have more libraries available 
> to you, or go with ruby 1.9.x to learn the latest greatest language 
> changes.  I think most people probably have 1.8.6 and 1.9.x installed 
> side by side(in python it would be 2.6.x and 3.x).    They probably use 
> 1.8.6 for their serious programs, and then they play around with 1.9.x 
> to learn the new stuff.

I have both installed but use only 1.9 simply because it is 
significantly faster and also because the new feature set seems better 
to me.  Since I am not using too many non standard libraries (and gems) 
the library lag is not an issue for me.

Kind regards

	robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/