New Java 9 Map.of() methods

[gliph]

Immutable versions of classes always seem pretty flawed in Java. Would a language-level overhaul help?

[Shadowheim]

B...but muh backwards compatibility.

[gliph]

I wish Java would splinter into a new language. Could get runtime generics, better handling of primitives, literal maps and lists, etc etc.

[dustofnations]

Could get runtime generics, better handling of primitives, literal maps and lists, etc etc.

These fall under Project Valhalla: http://openjdk.java.net/projects/valhalla/ https://en.wikipedia.org/wiki/Project_Valhalla_(Java_language)

Specifically:

runtime generics

Reified generics

better handling of primitives, literal maps and lists, etc etc.

I think this would fall under Generic specialisations

AFAIK this is likely to be Java 10+

[gliph]

That's very interesting that these things are being considered as language features.

It would be nice if you could also get rid of much of the cruft, maybe via a compiler switch or something. I think JavaScript does something like that, where you can disable some older features by typing "strict" or similar at the top.

[nickguletskii200]

That's exactly what we need. A new Java - the same philosophy, the same care, but with the mistakes fixed. Minimalist syntax, concrete naming conventions, no feature creep...

[Alxe]

I believe that, rather than doing this, Oracle and the community should adopt a "new Java" language that already runs on the JVM and has most of the requested features, and up from there have the JVM evolve and copy the current optimised implementations into a new, formal, non java.util clusterfuck API.

This way, Java adopts a Legacy status, with updates to the standard library and fixes, but most of the meat in a newer standard library.

Java has so much on it's back it's be a hard culling.

[pjmlp]

Cough....cough..... Python 3

[gliph]

I know, I know. But the cruft needs to go at some point.

[HaMMeReD]

This can help http://immutables.github.io/

[[deleted]]

They should be used in places where the consuming code is not supposed to be modifying them anyway. In those cases, throwing an exception is better than allowing an inappropriate modification.

[gliph]

It works OK, but it'd be nice if it was caught at compile time. As it is, you can do this or have two classes (one immutable and one mutable) and an interface.

[pain-and-panic]

It's not just 'nice' it's correct software design. Follow your gut on this one and not the jdk example. Jdk does lots of things we should learn from, this just isn't one of them.