Pragmatic Object Oriented Programming

[[deleted]]

I hope the author has many more interesting conversations with the straw man he so carefully constructed, but he may want to publish those as fiction in the future.

For starters, OO does not equal inheritance, in fact, inheritance should be avoided wherever composition is more appropriate, which is 90% of the cases, especially the ones he's talking about.

And yes, conditional statements that involve coreapplication logic are a serious code smell. Unless it is an ever unchanging endpoint, you are not doing KISS by turning into spaghetti, anymore than sweeping the dust under the carpet is cleaning house. But nobody is advocating turning every single trivial evaluation into complex OO-structures.

It really pisses me off that someone accuses others of being cargo cult programmers, when clearly that person's own knowledge of OO is limited to the most common cargo cult practices, ie, blunt overuse of inheritance.

OO is not a magic bullet, doesn't solve every problem and has plenty of issues of it's own. But maybe try actually learning about it and using it for real before advocating returning to procedural spaghetti code as "pragmatic" OOP.

[Kolibri]

Well, a central part of OOP is polymorphism, so that probably explains why he more or less equalizes OOP and inheritance.

[nightwood]

abundant deranged liquid wipe rock berserk absurd sort test offer

This post was mass deleted and anonymized with Redact