I found this presentation really interesting:
https://www.youtube.com/watch?v=kXcrClJcfm8
mainly because it seems to me that the industry is trending toward many, maybe
all, of the features of purely functional languages. No shared state, no shared
anything, we just pass values in and get values out of little abstract machines
that otherwise have no relationship.
But EOP starts with:
- always return self.
And its slogan is "tell, don't ask".
So it is prima facie the complete opposite of functional programming. All calls
*never* return a useful value. They always returns self, as a convenience for
chaining, but we already had the value of "self" wherever we called that from,
so we are advocating here a paradigm with *no functions*. No notion of
returning anything.
Pure Functional Programming is only functions. No shared state whatever, we
only call functions and return values. Particularly, there is no calling a
method on something to change state somewhere else.
EOP is no return values. All you have is calling methods on something to change
state, which you don't have access to. You can only provide it with the thing
it is going to share its value with, and then those things change each other's
state and so on.
These things appear to be really amazingly the opposite of each other, but
maybe they're just the same thing from opposite points of view. I can't decide.
--
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
---
You received this message because you are subscribed to the Google Groups "SD
Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
