Why to not use an IoC container

Whitebox is a profiler for an IoC container.

Think about that for a moment. Do you not think that when your solution for joining up components needs a profiler, your approach to building software might have gone just a little bit mad?

2 thoughts on “Why to not use an IoC container

  1. Nicholas Blumhardt

    Made me smile to read this 🙂 – yes, of course you’re right, but it seems like a problem we’re stuck with one way or the other. If you assemble them by hand you just use a regular debugger to find issues. A simpler way to build software probably calls for smaller apps with fewer components – problems of assembly/composition are probably symptoms rather than causes. Cheers!

    Reply
    1. Chris F Carroll Post author

      I’m glad you laughed – thank you for not taking offence!
      I guess if ‘wiring the pieces together’ was _all_ an IoC container did then it could all be vastly simpler, but managing lifecycles looks rather more complex. And in the end, software really is complex because the requirements are that complex.

      Reply

Leave a Reply to Chris F Carroll Cancel reply

Your email address will not be published. Required fields are marked *