Timeline for Dependency Injection vs Singleton Pattern
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 12, 2019 at 22:30 | comment | added | candied_orange | I've done DI with and without containers. If you do it properly, without letting clients know what DI container your using or employing a service locator, the benefit of the container boils down to encouraging the separation of construction code and behavior code (a good thing) by having you do construction in a different language (a dubious thing). Such as xml. You love xml right? | |
| Jul 10, 2019 at 3:12 | vote | accept | Bastien Vandamme | ||
| Jul 9, 2019 at 19:22 | comment | added | Sebastian Redl | @Fabio The difference between allowing and forcing ;-) | |
| Jul 1, 2019 at 2:23 | comment | added | Fabio | allows us to not reinvent the wheel - exactly what every new DI container does ;) | |
| Jun 30, 2019 at 3:45 | history | answered | jdewerth | CC BY-SA 4.0 |