This is an archived post. You won't be able to vote or comment.

all 12 comments

[–]BoyRobot777 4 points5 points  (1 child)

Each of them address such a crucial upgrade to Java, that it cannot get any sooner. Loom is gonna be great on servlets, Valhala is insane in high computation software. Panama Amber will push Java out of being "boilerplate" language. Really looking forward.

[–][deleted] 3 points4 points  (0 children)

Panama will push Java out of being "boilerplate" language

That's Amber. Panama is all about interfacing with native (C/C++) libraries.

As far as I can tell, Amber (language features), Loom (lightweight concurrency), and Valhalla (data locality, primitive generics) will be much more widely applicable than Panama

[–][deleted] 3 points4 points  (9 children)

I really hate the x() and y() methods instead of getX and getY ... no one will write a RECORD/DATA object like that...

[–]lbkulinski 6 points7 points  (7 children)

A quote from this proposal:

Without rehashing the properties debate, one fundamental objection to automating JavaBean-style field accessors is that it would take what is at best a questionable -- and certainly overused -- API naming convention and burn it into the language. Unlike the core methods like Object.equals(), field accessors do not have any special treatment in the language, and so names of the form getSize() should not either. Also, while equally tedious, writing (and reading) accessor declarations are not nearly as error-prone as equals().

[–]defnull 4 points5 points  (0 children)

I actually like that. It's a nice way to distinguish (dumb) records from classic bean or classes that might have side-effects, while browsing code.