Object-Oriented vs Function-Oriented Organization
I have a moderate degree of experience with both objected-oriented and procedural programming (as well as with functional programming). I _don't_ have much experience with systems large enough to make the benefits of each style of organization clear to me.

So what I'm wondering is, are there any general principles that can be used to gauge the applicability of a particular paradigm to a particular problem? (For example, objects vs closures vs plain variables for tracking state.) Examples and links to further discussion/reading recommendations are also welcome. I'm particularly thinking about high-performance game programming, but feel free to respond in another context.

I'm _not_ particularly interested in arguments about why one paradigm is better (or **not** better) than the other.

Sorry if this question is too general. I'm trying to get a handle on idiomatic programming to complement my knowledge of syntax.
Object-Oriented vs Function-Oriented Organization
===

I have a moderate degree of experience with both objected-oriented and procedural programming (as well as with functional programming). I _don't_ have much experience with systems large enough to make the benefits of each style of organization clear to me.

So what I'm wondering is, are there any general principles that can be used to gauge the applicability of a particular paradigm to a particular problem? (For example, objects vs closures vs plain variables for tracking state.) Examples and links to further discussion/reading recommendations are also welcome. I'm particularly thinking about high-performance game programming, but feel free to respond in another context.

I'm _not_ particularly interested in arguments about why one paradigm is better (or **not** better) than the other.

Sorry if this question is too general. I'm trying to get a handle on idiomatic programming to complement my knowledge of syntax.