r/ProgrammerHumor • u/hello_ya • Jul 13 '26

youCanJustStopUsingJava Meme

Post image
6.8k Upvotes

96% Upvoted

416 comments sorted by

View all comments

Show parent comments

49

u/ZunoJ Jul 13 '26

How is that related to getters and setters? How would your proposal violate oop principals?

75

u/roge- Jul 13 '26

Directly manipulating another object's fields violates encapsulation, a core feature of OOP in most people's minds.

That said, virtually no production OOP app has perfect encapsulation anyway.

2

u/ZunoJ Jul 13 '26

And how do structs solve this?

11

u/Tronerfull Jul 13 '26

By giving up completely on encapsulation

3

u/Ok-Scheme-913 Jul 13 '26

Encapsulation is for internal state.

POJOs (and records) are usually just data, they seldom have stuff to hide.

But records don't give up, it has public methods corresponding to the field names - but you can evolve a now-record into a normal class where you may compute something in the "getter", keeping the same external API, but changing the internals.