News for hackers. Stuff that matters.
Re:What Made OO Be Successful by chongli on Sunday January 04, 2015 @10:12AM (#8834590)
I should hope it'd be obvious to most people that you don't actually need all of OO just to get that little bit of syntactic sugar. I'd also like to point out another obvious fact: this idiom completely breaks down when the subject happens to be more than one person, i.e: steve_and_irene.drink(water) whereas it works fine in the procedural case (thanks to varargs): drink(water,steve,irene,...).
Re:What Made OO Be Successful by seanmcdirmid on Sunday January 04, 2015 @10:20AM (#8834615)
And you don't need syntactic sugar to do OOP, as you have just demonstrated with your examples. And also, multi methods exist, but you probably want one subject/dispatch variation per sentence anyways for complexity reasons.
Re:What Made OO Be Successful by PJDK on Sunday January 04, 2015 @06:29PM (#8836339)
Only if your model is terrible. It's perfectly possible to have thirsty_people.drink(water).
Re:What Made OO Be Successful by snlacks on Sunday January 04, 2015 @10:52PM (#8837140)
I think the more realistic code would be.

people.find('thirsty').drink('water')

Not about plain language reading, but instead writing code the way people think about actions and things.

Procedural is just as valid, but you use the right tool for the right job.