Timeline for When is it worth NOT using a Factory?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 20 at 5:32 | comment | added | guy mograbi |
You should default to not using factories - and then goes and uses a DI library..
|
|
| May 9, 2014 at 0:22 | audit | First posts | |||
| May 9, 2014 at 0:23 | |||||
| Apr 22, 2014 at 3:43 | audit | First posts | |||
| Apr 22, 2014 at 3:43 | |||||
| Apr 17, 2014 at 13:15 | comment | added | Scott Whitlock | Sometimes an object needs some dependencies (like services) that the object who wants to create it really doesn't need to know about. In that case, a factory can create objects for you without the caller knowing or caring what those dependencies are. Then when the dependencies change, you only have one class to change (the factory). | |
| Apr 16, 2014 at 18:27 | vote | accept | Dan | ||
| Apr 16, 2014 at 18:10 | history | answered | Telastyn | CC BY-SA 3.0 |