Skip to main content

Another look at Object Oriented versus Process Driven Design

Posted by johnreynolds on August 30, 2008 at 8:59 AM PDT

My friend Bob was troubled when I blogged "Object Only Programming is Silly". Bob knows from experience that life after OO is dramatically better than life was before OO... so my criticisms just don't sit well with him. Obviously I must have gone off the deep end :-)

If you're interested in Bob's thoughts and my reply, check out my ramblings: Another look at Object Oriented versus Process Driven Design.

Related Topics >>

Comments

"It appears to me that you are simply advocating application logic" Close... I am advocating that you start with the application logic. If the business is not capable of supporting the required application logic, then you'll know exactly how you need to improve your business capabilities. I'm not "anti-object"... I'm anti-objects-for-the-sake-of-objects. -JohnR

I'm interested in your arguments. They fit closely with the arguments of people who advocate closures. However, that's not good enough for me. I personally advocate a strong distinction between application logic (what the user wants to do) and business logic (what the business is capable of doing). It appears to me that you are simply advocating application logic: what does the user need to do in order to solve a problem. if so, the object is an application. Think of it as a web service if you like. At the application level, who cares about object orientation? You only want to solve a problem, so publish an interface to methods that solve the problem, and call them from the user interface of your choice. From those methods, call the business logic necessary to produce the desired result. Who cares where those business methods live? They could be in web services, or they could be in a local library. I think this is the concept behind SOA, or am I missing your point?