This post originated from an RSS feed registered with Java Buzz
by scot mcphee.
Original Post: OO theory and practice considered harmful?
Feed Title: SystemExxception()
Feed URL: http://www.autonomous.org/pebble/systemexxception/rss.xml?category=Java
Feed Description: java design and culture by scot mcphee
Via Straight Talking Java comes a link to an article on DevX, 'OOP Is Much Better in Theory Than in Practice'. I couldn't disagree more with this article. In fact it has so many misrepresentations and errors that it horrifies me to think that a technical journal would stoop to tabloid journalism to gain readers through misdirected controversy. Well, maybe that's more common than I think.
This is really the key sentence where the argument really starts to completely unravel;
A frequent argument for OOP is it helps with code reusability, but one can reuse code without OOP-often by simply copying and pasting.
Yes folks, OO is overkill because you can reuse code by duplicating in 100 different places in your code! No, the fact that if you want to change that algorithm now means you have to change it 100 times (mistake prone), is not an objection. Cut and paste away fellows!
Previous Topic
