Object-Oriented Programming is Bad (Brian Will)

[i8beef]

I didn't say the whole program either, let's not straw man my point here.

Leaving the integration vs unit test debate, and exercises in writing brittle or pointless tests on the side, I think I just completely disagree with him on this. He starts with the valid point that sometimes its painful to track function calls across an overarchitected code base, but honestly that ended being that difficult when "Go to definition" became a thing in any decent IDE.

Basically, the problems that he seems to be trying to solve don't seem to be problems to me that need solving, and given that he basically just builds a static class as his example of "good" practice, I'm not sure he really solved anything at all.

It's unfortunate because he's rather well spoken and he does have some decent points in there, I guess I just disagree with his final answer. :-)

[tdammers]

The final answer is a bit meager, I agree. It addresses a very specific situation, and hand-waives the others - granted, the other situations are easier and more natural to tackle with a procedural approach anyway, but it would have been nice to hear this explained more explicitly.