3 ms·
I've written my rebuttal here: http://axilmar.blogspot.gr/2014/10/object-oriented-programming-is-disaster.html http://axilmar.blogspot.gr/2014/10/object-orient
by axilmar 12y ago
I've written my rebuttal here:
http://axilmar.blogspot.gr/2014/10/object-oriented-programming-is-disaster.html http://axilmar.blogspot.gr/2014/10/object-oriented-programmi....
- chris_wot 12y agoThat's awesome :-) but... how did you manage to get through that massive rant and extract the author's main points?
- axilmar 12y agoI just read it, skipping the non-essential parts, after quickly scanning them. I might have missed one or two points, but it doesn't really matter.
- nbevans 12y agoYou don't come across well in this at all. 200 classes in a OO project is pretty small really. And you've never used DI ever? Really?
- peterashford 12y agoI've written large systems in Java, C++ and yes, I have never ever used DI. Nor even seen any kind of AbstractFactory in Java.
- nbevans 12y agoI don't believe you. Are you mistaking DI for meaning a full blown IoC framework? DI is merely the abstract computer science concept. In FP land we call it partial application or P/A. But it is essentially the same thing. I honestly cannot fathom how a large project would look without DI. It must be hideous with massive amounts of coupling all over the place i.e. not something to be proud of. Refactoring must be very hard. I would have to take a few guesses to know what an AbstractFactory is. That is a "J2EE Javaism" and always has been. So you aren't alone there ;)
- TheCoelacanth 12y agoI'm pretty sure it's impossible to write a non-trivial program without ever using DI, even if just by accident.
- nbevans 12y agoAgreed. If you've not used DI after 15 years as a "professional" developer, and you are also happy to "boast" about this fact on the Internet, then it means you are very likely an utter shit developer.
- wtetzner 12y agoAre you sure you know what DI is? It just means you pass an object's dependencies to it, instead of it constructing them itself. You don't need a framework to do DI.
- axilmar 12y agoI have never used DI in my 16 year professional career in C++ and Java land.
- nbevans 12y agoYou should blog about your alternative approach to structuring code bases that minimise coupling. It may be superior.