this post was submitted on 25 Oct 2025
64 points (100.0% liked)

Programming

23307 readers
247 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] FishFace@piefed.social 6 points 6 days ago (1 children)

Agreed. And a lot of it is working around limitations of whatever version of Java was common at the time.

"Visitor pattern" is better implemented as an implementation of Iterator or whatever your language calls that. Everyone knows what "for x in thing" means, but wtf does it mean to "visit" something?

[–] tias@discuss.tchncs.de 5 points 5 days ago* (last edited 5 days ago)

I'd say most of the GoF patterns evolved in a C++ toolchain (and then the Java junior devs started a cargo cult around them that has survived to this day). The book was never as language-independent as the authors envisioned it to be—in fact I'd argue that with the right programming language design the patterns happen implicitly or are obsolete.