this post was submitted on 10 Oct 2024
49 points (85.5% liked)

Programming

17291 readers
200 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] JackbyDev@programming.dev 3 points 2 weeks ago (1 children)

Why is the word factory a code smell?

[–] xigoi@lemmy.sdf.org -2 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

It means you’re compensating for the lack of optional/named parameters in your language.

[–] magic_lobster_party@fedia.io 3 points 2 weeks ago

Sounds like you’re thinking more about the builder pattern.

[–] Traister101@lemmy.today 2 points 2 weeks ago

Eh? How's that work. I'm not going to sit here and say there isn't too many factories in Java but as a concept it's extremely useful. You hand off a "factory" to something which actually creates the object. This is really useful in for example serialization. How so? You could register factories (mapped to some sort of ID) which get passed the serialized data and return some sort of created object. Now the core serialization code doesn't know nor care how exactly any particular type gets serialized. Pretty nifty huh?

Some languages have better ways to encapsulate this functionality but that's what the factory concept is