3 ms·
If FactoryFactories are so bad, why do Java and C# devs (even "smart" ones) still use them? Harder to decompose = more job security?
by mistermann 10y ago
If FactoryFactories are so bad, why do Java and C# devs (even "smart" ones) still use them? Harder to decompose = more job security?
- humanrebar 10y agoI think much of the problem with FactoryFactories is naming them FactoryFactories. We don't call processes 'ProgramCounterContextCollections'. The pattern isn't bad, in fact flavors of it (if you squint) are used regularly even in low-level C systems code.
- jerven 10y agoRuntime loading of code by frameworks leads to Factory objects. e.g. database drivers. The only factory factory I know of is in the Spring runtime dependency injection framework.