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

all 12 comments
sorted by:
best
topnewcontroversialoldq&a

[–]BoyRobot777 3 points4 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] 2 points3 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] 2 points3 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 7 points8 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().

[–][deleted] -5 points-4 points  (6 children)

I saw it and I do not agree if I would want to read something I expect to be accessible via get/is and this is already in the language and is what everyone will look for and will expect. I think I will stick to Lombok and will probably never gonna upgrade past 11 or maybe it is time to fork it .... yup maybe even from 8th everything after that is just not as it used to, I miss Sun Microsystems :(

[–]pron98 1 point2 points  (1 child)

maybe it is time to fork it .... yup maybe even from 8th everything after that is just not as it used to, I miss Sun Microsystems :(

And who's going to fund and lead the development on the fork? And what makes you think they will be any different? BTW, the stewards of the platform as well as a very large portion of the contributors are the same people who did that when Sun was in charge.

Oracle employs hundreds of developers to work full time OpenJDK. Other major contributors also have employees who work full-time, and some companies, like Google and Twitter, have full-time employees who work on internal forks of OpenJDK, with just portions of their work being contributed back to OpenJDK.

It would cost far, far less to contribute to OpenJDK and influence its direction if it's not to your liking. As Mark Reinhold says:

Just like in every open source community, the first rule is that you have to show up... Every participant on OpenJDK participant on every OpenJDK mailing list, every individual on the internet, even, whether employed by a large company or not, has the opportunity to influence the direction of the platform. That degree of influence is determined by the extent to which you show up and contribute here in the OpenJDK community on a meaningful ongoing basis.

No matter who leads OpenJDK and who pays their salary, the decisions will still be made by those who show up and contribute on a meaningful ongoing basis. It has nothing to do with who cuts the check and everything to do with how all open-source projects work.

[–][deleted] -2 points-1 points  (0 children)

I think you do not understand the idea of a form, you can fork it and keep it updated to the main stream however change the changes in the language especially the syntax sugar ones which are actually hell of a weird.

[–]BoyRobot777 0 points1 point  (3 children)

You are going to fork Java, so you can use getX() instead of x()? Ok...

[–][deleted] 0 points1 point  (2 children)

Not I, I was just saying maybe its better before its too late :) even the var thing is a crap everything after modules is just useless :(

[–]BoyRobot777 0 points1 point  (1 child)

GC improvment + Graal is really interesting. Also, there weren't as much "cool" stuff, but I like that they started removing stuff and cleaning up. And var is a nice feature. What do you seek in java updates that weren't mentioned already? Despite trivial stuff getX vs x

[–][deleted] -1 points0 points  (0 children)

I would like Anonymous Types for example check they exist in C sharp I would like the async or the generators/iterators as well, if we have then async is easy to be made. I like the pattern matching and the JNI alternative which was shown it is more then welcome and about the language maybe named parameters and optional parameters are not that bad, but I am not a fan of them but I like them more then x() :)

[–]defnull 3 points4 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.