@sstevenson638
I heard one statement from this that helped me understand one of their reasons for making value class fields final. "If they are final they can be cached without fear of them changing". I've been ragging on the Java designers about making value class fields final. I admit that my understanding of modern hardware architecture is dated and I don't understand how performance optimization takes place under the hood. I hope you will put out some videos or other information to help developers understand so they can write more highly optimized (or optimizable) code. I once had an outside consultant tell me not to worry about performance optimization when designing application architecture. I thought to myself "this guy is an idiot". I've been writing performance engineering codes since the days of FORTRAN and I can tell you that they way you organize memory and data has a huge impact on performance, especially with huge data models and numerical solvers.
@gs-e2d
Good Good Good, performance of serialization will also improve, since we get a chance for new serialization.
@redcrafterlppa303
For serializable value types you could require it to specify such external constructor. Marking it with an annotation seems like the logical choice as serialization is already using annotations to mark things. So it's not a new concept.
@TheSpeedX
Interresting
@cya3mdirl158
Im waiting for named args
@dnbhatia85
Java people on big mission.. I think they want just two line code to create SPA.
@tvb4026
java needs complete rewrite full new version like javascript or dart
@shadeblackwolf1508