News for hackers. Stuff that matters.
Re:Ask HN: Why choose a dynamically typed language? by pbiggar on Saturday August 07, 2010 @06:11PM (#1584439)
I wouldn't say that it has _nothing_ to do with monkey patching. Monkey patching is the ability to update classes members dynamically. Duck typing is the ability to update an object's members dynamically. Since the overall point is to dynamically create a new member of some object, I think the previous poster can be forgiven.
Re:Ask HN: Why choose a dynamically typed language? by spooneybarger on Saturday August 07, 2010 @07:18PM (#1584548)
Duck typing isn't the ability to update an object's members dynamically. There is nothing inherent in the meaning of duck typing that says anything about updating. All it says if i ask:

walk and talk of it and can walk and talk then as far as i'm concerned, its a duck because that is what a duck was expected to do.

duck typing is polymorphism w/o inheritance.

Re:Ask HN: Why choose a dynamically typed language? by pbiggar on Wednesday August 11, 2010 @05:18AM (#1594250)
> walk and talk of it and can walk and talk then as far as i'm concerned, its a duck because that is what a duck was expected to do.

This doesn't even parse.

Duck-typing is the idea that an object's type at a particular time is made up of the set of fields and methods it has _at that time_. I suppose that doesn't strictly require updating, but it would be a pretty lame duck with it.

Polymorphism w/o inheritance is a fine description. How do you think that can be accomplished without dynamic updating?