From: Francis Cianfrocca <garbagecat10@...>
Date: 2007-06-16T02:16:05+09:00
Subject: Re: Ruby Nube

------=_Part_41422_5480354.1181927756665
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 6/15/07, Bill Man <a.paranoid.android@gmail.com> wrote:
>
> Hello,
>
> The concept of Dynamically Typed Languages has peaked my interest.
> However, I have spent sometime trying to find what problem they exactly
> solve.  Can anyone tell me:
>
> - What problems do dynamically typed languages such as Ruby solve?
> - What is the business proposition for using a dynamic language such as
> Ruby over Java / C#?
> - What kinds of things can be better with dynamic languages such as
> Ruby?



Dynamic typing is based on the intuition that the language system itself can
discover the types you intended to use. If you're a dyed-in-the-wool
static-language programmer like me, this notion sounds nothing short of
insane at first. As it turns out, however, not only is it essentially
correct, but the errors you make under dynamic programming are not usually
difficult to find.

Dynamic typing is one of those few things that seem like they must be wrong,
but then surprise you by how right they are.

For the first two years after I learned Ruby, I wrote Ruby programs that
looked like uglier versions of C programs. Then the penny dropped. Now my
only real problem with Ruby is its abysmal scalability to large data sets.

------=_Part_41422_5480354.1181927756665--