Java Language update By Brian Goetz

In this illuminating session, Brian Goetz, the Java Language Architect, delves into the latest advancements and features that are shaping the future of the Java programming language.
BRIAN GOETZ
Brian Goetz is the Java Language Architect at Oracle and was the specification lead for JSR-335 (Lambda Expressions for the Java Programming Language). He is the author of Java Concurrency in Practice and over 75 articles about Java development.

[@stephankolle9705]

It's so good to have Brian Goetz as one of the Leaders of java

[@KangoV]

Fascinating! Some amazing features on the way. Great talk! I really like the "with" pattern for records being able to provide deconstruction and then construction without having to code it. I achieve the same thing (sort) of with builders and a change method ..... change(UnaryOperator func);

[@AnthonyGoubard]

About the last question of the backward compatibility of Java and the renaming of the Swing packages: As far as I can remember Swing was an external library first with Java 1.1. It's when it was added to JDK 1.2 that the packages were renamed to javax.swing... So it's not like if it was already in the JDK and then renamed.

[@TJ-hs1qm]

Are records the equivalent to case classes in Scala (aka type constructors)?

[@techaido]

Java is closer to Scala :D. ... Good Job.
Please continue removing the overbossity

[@ebuzertahakanat]

Bring back JAOTC!

[@user-jw8jn7lh8c]

yippie!

[@hsjawanda]

The chief complaint against Java is its verbosity (I like Java, mostly). Can be solved by making Lombok-like functionality (Records are great but not as widely usable as Lombok's code generation) a part of the compiler & allowing default values for method parameters. What are the arguments against these two?

[@terribleprogrammer]

First complete Valhalla

[@ingframin]

Java is becoming more like Haskell. I like it!😎

[@agcouper]

My thoughts exactly!

[@hareepjoshi]

No one touches scala with a 10 foot pole and you’re dreaming of Haskell?😅

[@uncle_slashes]

Nobody care about Valhalla?

[@simonk1844]

Wow, that templating feature is ugly, non-orthogonal, and non-extensible. Could nobody come up with a better solution?
For example, how about introducing something like Scala's apply methods: an object reference can be invoked in function syntax eg "formatter(args...)" which invokes formatter.apply(args). That seems a much more generally useful feature which can then be used to provide STR("""....""") for string templates.

[@gsit80]

I don't like where is going.

[@gsit80]

I don't understand Record.
We have POJO.