...but the elders still decree Java will never be granted ergonomics QoL improvements like getters/setters because...? At this point it feels like their pride is at stake.
...but the elders still decree Java will never be granted ergonomics QoL improvements like getters/setters because...? At this point it feels like their pride is at stake.
I don't understand what you're saying. Java records don't need getters/setters. If you want that interface there's lombok.
Records is a very new addition. lombok is writing bytecode directly to facilitate that.
wut? Java has always had getters and setters
Downvoted for stating an objective fact?
(I didn’t downvote you)
In my post, I’m referring to Java’s refusal to adopt “properties” (i.e. methods invoked using the same syntax used for fields) like VB, C#, JavaScript, Swift, et cetera.