Thinking in FP vs OOP for large scale apps => Re: [plt-scheme] Imperative programming : missing the flow

On 5/16/07, Robby Findler <robby at cs.uchicago.edu> wrote:
> On 5/16/07, Grant Rettke <grettke at acm.org> wrote:
> > > Thanks.  As you said, choosing the best abstraction for the job and that OOP
> > > is best today because it's most familiar - we are in agreement here.  My
> > > question for asking these questions isn't to debate that point, but rather
> > > to educate myself on another paradigm ( i.e. FP), so I can intelligently
> > > choose the best abstractions - otherwise the best abstraction (i.e. OOP most
> > > of the time) is best only because it's most familiar.
> >
> > Sorry for beating on that point, that wasn't actually my actual intention.
> >
> > When you read about modules and units, and how you can expose their
> > interface, you immediately recognize that idiom coming from OOP.
>
> I'm not sure that this statement is historically accurate.

Boy I can't get away with being lazy in this group huh? :)

The point which I didn't express was that the notion of maintaining a
state within a 'module' that is exposed via an 'interface' is
something that seems to be a commonality among OO and modules/units.