3 ms·
...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 i
by DaiPlusPlus 1y ago
...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.
- stickfigure 1y agoI don't understand what you're saying. Java records don't need getters/setters. If you want that interface there's lombok.
- ok123456 1y agoRecords is a very new addition. lombok is writing bytecode directly to facilitate that.
- peterashford 1y agowut? Java has always had getters and setters
- peterashford 1y agoDownvoted for stating an objective fact?
- DaiPlusPlus 1y ago(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.
- peterashford 1y agoRight. They're usually called properties, rather than getters and setters.