An example would be how the IBM J9 JIT converts a final Point class, just with getters and setters into a value type.
Also there are language extensions from JVMs like IBM Packed Objects or Azul Object layouts that are exploring how to involve the language into value types.
It sucks that they didn't follow the route of Mesa, Modula-3, Eiffel and Oberon in regards to value types, but they aren't holding still.
But then you also need data structures that can be parameterized to store such value objects as values. Otherwise you're back to square one.
https://en.wikipedia.org/wiki/Project_Valhalla_(Java_languag...
The Java language is definitely not set in stone.
If (and that's a big if) they introduce value types in 2018, it will have been almost 25 years since that fateful decision that has done so much damage.
Go owners have millions and millions of lines of existing Java code and they employ many people whose entire careers were made on top of Java.
I'm not saying there are no rational reasons to prefer Java over Go. But Google is hardly the yardstick for that.
That makes me wonder about your universe of things to consider. Java's terrible memory usage was set in stone the moment they decided not to include structured value types.