How's ruby compare to it older brother python

[Cameron Laird]

In article <c6jg7404m at enews4.newsguy.com>,
Phil Tomson <ptkwt at aracnet.com> wrote:
			.
			.
			.
>Your best bet is to actually use each language for a small project 
>so that you spend about a day with each language.  You'll find that while 
>on the surface both languages seem quite similar, at a deeper level they 
>each have a very different effect on how you think about and approach the 
>problem.  Some people find that Ruby best fits with their brain and others find 
>Python a better fit.  You won't know until you try.
			.
			.
			.
It's not just that "You won't know until you try" ("is it better
to have children, or join the monastery?"); it's that you won't
know until you try, *and it's inexpensive to try*!  It's eminently
feasible to gain experience in either language with a few hours (!)
of work, as opposed to the weeks that must precede enlightenment
about, say, J2EE servers.
-- 

Cameron Laird <claird at phaseit.net>
Business:  http://www.Phaseit.net