The neat thing is, you can add stuff like range checks and logging for getters and setters without changing every call. Separation of concerns is also vital in larger projects.
typical OOP progaganda
also const correctness in languages that support that concept
Yeah, I need to force myself to do it, cuz it feels so slick and efficient and overall nice. Or am I just dumb and didn't understand satire of this post.
That's not a new way to change data, it's reading it.
Wait until you hear about the concept of properties in languages like Javascript, C#, Kotlin and many others.
At least for Kotlin it's literally just syntactic sugar for getter and setter methods. I really like them, don't get me wrong, but it's just the bottom approach masquerading as the top approach
I am triggered
Imagine not using a language with setters and getter built in lol
I love dart's approach to getter and setter methods... They let you define methods labelled explicitly as "get" or "set" methods that you can call without writing the parentheses. So the call looks like accessing a member variable, but internally it can handle additional functionality like logging or validation or whatever you want. So the syntax would look like the first example in the meme, but with all the benefits of the second example. I wish more languages would incorporate this
Every IT profesor, ever
