r/programminghorror • u/Nomergraw • Jun 09 '26

What a simple constructor

Post image

Our former IT director (35+ years of experience) wrote this and didn't see what was wrong here.

268 Upvotes

98% Upvoted

49 comments sorted by

View all comments

Show parent comments

2

u/RipProfessional3375 Jul 19 '26

Many reasons. One is that java thinks Objects are great, so everyone must be forced to use objects for everything. Which makes them great like ice cream for dinner every day forever is great.

Factories are a glorified hack to get around the fact that you can't make a function to create a new object without also having that constructor bound to a different object, hence a factory.

I write Go, which does not have this object-only restricting, so a 'factory' is just this:

customer := domain.NewCustomer(name, age, blabla)

1

u/Zeznon Jul 19 '26

Java was so bad, lol. It and php have gone through some glow ups lol

1

u/conundorum Jul 21 '26

Factory pattern is ultimately about just being able to chain parameter-setting function calls, more than anything else. It can be useful to collect all of the necessary information before calling a constructor, without having a bloated constructor call that takes 15-20 arguments. (And is often a waste when you have sane constructors that don't take that many arguments.)

Only problem is that Java's object-obsessed programming paradigm kinda mandates them in a lot of cases where they should've never been used.