The language has evolved a lot since the "enterprise" Java days. Much of the unnecessary ceremony was relaxed, and it became less religiously adherent to the idea that it was simply a compiled, statically typed successor to Smalltalk.

▲

DaiPlusPlus 2 days ago | parent [-]

...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 2 days ago | parent | next [-]

I don't understand what you're saying. Java records don't need getters/setters. If you want that interface there's lombok.

	▲	ok123456 2 days ago \| parent [-]
		Records is a very new addition. lombok is writing bytecode directly to facilitate that.

▲

peterashford 2 days ago | parent | prev [-]

wut? Java has always had getters and setters

▲

peterashford a day ago | parent [-]

Downvoted for stating an objective fact?

	▲	DaiPlusPlus a day ago \| parent [-]
		(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.