this post was submitted on 05 Jun 2026
101 points (96.3% liked)
Programming
27259 readers
87 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Modern OOP is an antipattern.
OOP isn't an anti-pattern, but the way it's used in the enterprise Java world definitely is. And it's all based on a fundamental misunderstanding of what an interface is.
Elaborate
The fedora prevents them from typing fast enough.
Probably a cat-v reader
When was that published?
cat-v is a weird corner of the internet, don't try to read it as a contemporary serious opinion piece. See https://harmful.cat-v.org/software/
I was wondering, it reads like old man shakes fist to clouds.
Harmful: compilers
Better alternative: magnetized needle and a steady hand
From my understanding, anti OOP aficionados say too much energy is spent constructing the framework, often unnecessarily, instead of writing the code that needs to be done. I think they have some merit in their argument. It's easy to see both points of view.
Mutation (or not) is a matter of runtime semantics, not surface semantics. Let the compiler figure it out. (Functional-but-in-place c.f. Koka, Roc, Lean4)
Purity and referential transparency make writing correct, zero-maintenance code easy.
Although you can extract a lot of money from your customers if you deliver inscrutible code that needs a lot of maintenance.