Your Code: OOP or POO?

Previous | Next

Your votes power DZone. Login and vote now.

By gst
via codinghorror.com
Published: Mar 05 2007 / 04:12

I'm not a fan of object orientation for the sake of object orientation. Often the proper OO way of doing things feels like a productivity tax. Sure, objects are the backbone of any modern programming language, but sometimes I can't help feeling that slavish adherence to objects is making my life a lot more difficult. I've always found inheritance hierarchies to be brittle and unstable, and then there's the massive object-relational divide to contend with. OO seems to bring at least as many problems to the table as it solves.

Vote up

Vote down

11
0
1165
451

Save Send Tags: methodology, opinion

Upcoming Links

See all the newest links

Comments

Add your comment

pavelgj replied ago:

0 votes

The problem is not with the tool, it with how you use it. A hammer is great for driving in nails but if you hold it up-side-down it's going to make your life miserable.

If you are a sloppy programmer with poor code style habits, narrow/locally oriented thinking, just stay away from OOP. I guess you also have never heard of or don't understand or just don't use the Design Patters (http://en.wikipedia.org/wiki/Design_pattern_(computer_science)).

Well, I gotta agree that there are people (I've met a few) who just can't wrap their head around OOP. Especially if you've always been an RPG or Lisp programmer.

I also somewhat agree with the point of "OOP abuse", using it for the wrong reasons, but this just comes back to everything I wrote before... Either you're a sloppy programmer or you just don't get it...