News for hackers. Stuff that matters.

A comment on Java 25's new CPU-Time Profiler (1). Parent comment

Re:Java 25's new CPU-Time Profiler (1) by DaiPlusPlus on Saturday September 13, 2025 @07:24PM (#45236131)
...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.
[ Parent | on HN ]
Re:Java 25's new CPU-Time Profiler (1) by stickfigure on Sunday September 14, 2025 @12:36AM (#45237474)
I don't understand what you're saying. Java records don't need getters/setters. If you want that interface there's lombok.
[ Parent | on HN ]
Re:Java 25's new CPU-Time Profiler (1) by ok123456 on Sunday September 14, 2025 @04:06PM (#45242806)
Records is a very new addition. lombok is writing bytecode directly to facilitate that.
[ Parent | on HN ]
Re:Java 25's new CPU-Time Profiler (1) by peterashford on Sunday September 14, 2025 @03:16AM (#45238138)
wut? Java has always had getters and setters
[ Parent | on HN ]
Re:Java 25's new CPU-Time Profiler (1) by peterashford on Sunday September 14, 2025 @04:50PM (#45243120)
Downvoted for stating an objective fact?
[ Parent | on HN ]
Re:Java 25's new CPU-Time Profiler (1) by DaiPlusPlus on Sunday September 14, 2025 @09:35PM (#45245173)
(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.

[ Parent | on HN ]
Re:Java 25's new CPU-Time Profiler (1) by peterashford on Wednesday September 17, 2025 @11:06PM (#45284767)
Right. They're usually called properties, rather than getters and setters.
[ Parent | on HN ]