I think the problem with this terminology is that it's not direct enough. Like why do you require people to understand a metaphor (factory -> make things) while coding? Just name the thing makeX or makeXMaker.
Oh, that'd just be a NewThing() constructor. The ThingFactory() can probably take an argument specifying which implementation you need. It's almost always just a small function holding a conditional chain that you don't want to copy/paste all over the place. As a bonus, it's a named design pattern that you can find in basically any book about design patterns.
Whether it's actually worth using is another question, but at least it's a point of reference.
That's because it's standard terminology that means more than just 'making things'. There is also the Builder pattern which also makes things but which is not the same as a Factory. Besides, the word maker sounds weird.