Peter Uhnak wrote > Scale can make all the difference.
I don't think it should. If you have a small cluster of objects where you can manage the dependencies yourself, you can compose larger objects from them and manage the dependencies the same way. By doing so, you'll get an object that is simpler from the outside than it's parts in the inside, and you'll need to solve the smaller problem again. In other words we shouldn't write large software, but compose large software from smaller ones. But the same can be done with objects (that's why I'm not a big fan of microservices despite they solve this problem similarly). If you have a flat structure (where objects don't form higher level abstractions) and everything needs to know about everything else, then the DI container will make it easier to work with this structure. But I don't think this is the right way to organize a software. -- View this message in context: http://forum.world.st/Wiring-objects-IoC-and-Service-Locator-tp4949280p4950535.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
