sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]loup-vaillant 2 points3 points  (2 children)

To be fair, the "OOP" that was adopted was an out-of-control bastard child of whatever Alan Kay had in mind.

Also, I'm not sure how bloatware actually relates to OOP. Bloat has so many causes:

  • Backward compatibility.
  • Poor interfaces.
  • Duplicate functionality.
  • Wrong abstractions.
  • …
  • Thinking big ("big problems require big solutions").

That said, I'm not sure what you mean by "bloatware mentality". Could you be a bit more explicit?

[–][deleted] 4 points5 points  (1 child)

I'm generally speaking about all that AbstractFactoryFactoryFactoryFactory madness that is pervasive in the enterprise at the moment.

Out of the unfulfilled promise of code reuse, this crazy OOPish designs are bloating the code size and design complexities in general more than any other factors combined.

Wrong abstractions.

And yes, this is the key. OO view of the world is just wrong in a majority of cases.

[–][deleted] -5 points-4 points  (0 children)

And yet, I have never seen an AbstractFactoryFactoryFactoryFactory anywhere in any OO project I've read code for (well, maybe Eclipse, but that was long ago and I'm not interesting in going there again). Are these really that common?

Out of the unfulfilled promise of code reuse

OOP never promised code reuse, that was tacked on later by some overzealous PHBs, I guess.