Brian Goetz's guest appearances

Brian Goetz

Software Engineering Radio - the podcast for professional software developers

The InfoQ Podcast

Chariot TechCast

JetBrains Connect

Colin Eberhardt

Rod Johnson

Ashley Williams

Jessica Kerr

Bryan Liles

Lin Clark

Cathy O'Neil

Brent Vatne

Steve Klabnik

Mike Lee

Michael Feathers

Kent C. Dodds

Steve Smith

Arun Gupta

Anastasiia Voitova

OwlTail

Trisha Gee

In this episode, Brian Goetz, Java Language Architect at Oracle, and Trisha Gee, Developer Advocate and Subteam Lead for Java Advocacy at JetBrains discuss and debate the status of Java in the modern world with our host, Paul Everitt.

In this episode, Brian Goetz, Java Language Architect at Oracle, and Trisha Gee, Developer Advocate and Subteam Lead for Java Advocacy at JetBrains discuss and debate the status of Java in the modern world with our host, Paul Everitt.

"Moving Java Forward" with Brian Goetz and Trisha Gee

In this episode, TechCast host Ken Rimple and Chariot consultant Will Vuong are in conversation with Brian Goetz. Brian heads up the Java language team at Oracle, and is one of our two keynotes for the year at Philly ETE 2019.  Ken and Will ask Brian about where the language is headed in version 13, and find out more about how the Open JDK project is organized. They discuss the current JDK development process, how Oracle developers work on the OpenJDK to move language features forward, the “Propose to Target” stage and the JEP release candidate steps in accepting a new feature. They also cover upcoming features like Project Amber, Project Valhalla, and Project Loom. If you missed Brian’s talks at ETE (or just want to re-watch them), you can find a video recording here:  Keynote: FP vs. OOP (Choose Two) Java Futures, Early 2019 Edition  Also – don’t forget to listen on to the end of the podcast, where we offer a discount code for registering as a TechCast listener. The post TechCast #112 – ETE 2019 Keynote Speaker Brian Goetz appeared first on Chariot Solutions.

In this episode, TechCast host Ken Rimple and Chariot consultant Will Vuong are in conversation with Brian Goetz. Brian heads up the Java language team at Oracle, and is one of our two keynotes for the year at <a href="http://phillyemergingtech.com" rel="nofollow" target="_blank">Philly ETE 2019</a>.  Ken and Will ask Brian about where the language is headed in version 13, and find out more about how the Open JDK project is organized. They discuss the current JDK development process, how Oracle developers work on the OpenJDK to move language features forward, the “Propose to Target” stage and the JEP release candidate steps in accepting a new feature. They also cover upcoming features like Project Amber, Project Valhalla, and Project Loom. If you missed Brian’s talks at ETE (or just want to re-watch them), you can find a video recording here: <ul> <li><a href="https://chariotsolutions.com/screencast/philly-ete-2019-keynote-brian-goetz-fp-vs-oop-choose-two/" rel="nofollow" target="_blank">Keynote: FP vs. OOP (Choose Two)</a></li> <li><a href="https://chariotsolutions.com/screencast/philly-ete-2019-brian-goetz-java-futures-early-2019-edition/" rel="nofollow" target="_blank">Java Futures, Early 2019 Edition</a></li> </ul> Also – don’t forget to listen on to the end of the podcast, where we offer a discount code for registering as a TechCast listener. The post <a href="https://chariotsolutions.com/podcast/techcast-112-ete-2019-keynote-brian-goetz/" rel="nofollow" target="_blank">TechCast #112 – ETE 2019 Keynote Speaker Brian Goetz</a> appeared first on <a href="https://chariotsolutions.com" rel="nofollow" target="_blank">Chariot Solutions</a>.

TechCast #112 – ETE 2019 Keynote Speaker Brian Goetz

On this week’s podcast, Wes Reisz talks with Brian Goetz. Brian is the Java Language Architect at Oracle. The two start with a discussion on what the six-month cadence has meant to the teams developing Java. Then move to a review of the features in Java 9 through 12. Finally, the two discuss the longer-term side projects (such as Amber, Loom, and Valhalla) and their role in the larger release process for the JDK.* The JVM’s sixth-month cadence changed the way the JDK is delivered and planned. While it definitely provides more rapid delivery at expected intervals, the release train approach turned out to also improve flexibility and efficiency.* Oracle JDK and OpenJDK are almost identical. Most of the JDK distributions are forks from OpenJDK with different bug fixes and backports applied. So the difference between the distributions now is largely which bug fixes are picked up.* Local Variable inference (which was released as part of Java 10) illustrated the tension on making changes to the language. Many people wanted the change, but many others felt it would enable people to write bad code. Oracle had to balance the two views when making the change.* The number of Java versions allow finer grain decision making on what is appropriate for an application. With the adoption of containers, applications are bundled with an exact JDK version rather than having to use one from a systems level. The different versions give developers more options.* Incubating features are new libraries added to the JDK. They were offered starting with Java 9 as a way for people to test and offer feedback more rapidly. With Java 12, preview features will be released. Preview features are similar but are core platform and language features.* Shenandoah and ZGC are both low latency garbage collectors. They originally came from different sources. While both garbage collectors are similar, each has different performance characteristics under different workloads. The two garbage collectors represent options available to JVM developers.* Most non-trivial JDK features take more than six months to develop. Longer term side projects like Amber, Loom, Valhalla are where these features are developed prior to being released with a version of the JDK. The projects range from language enhancements to concurrency work.

On this week’s podcast, Wes Reisz talks with Brian Goetz. Brian is the Java Language Architect at Oracle. The two start with a discussion on what the six-month cadence has meant to the teams developing Java. Then move to a review of the features in Java 9 through 12. Finally, the two discuss the longer-term side projects (such as Amber, Loom, and Valhalla) and their role in the larger release process for the JDK. * The JVM’s sixth-month cadence changed the way the JDK is delivered and planned. While it definitely provides more rapid delivery at expected intervals, the release train approach turned out to also improve flexibility and efficiency. * Oracle JDK and OpenJDK are almost identical. Most of the JDK distributions are forks from OpenJDK with different bug fixes and backports applied. So the difference between the distributions now is largely which bug fixes are picked up. * Local Variable inference (which was released as part of Java 10) illustrated the tension on making changes to the language. Many people wanted the change, but many others felt it would enable people to write bad code. Oracle had to balance the two views when making the change. * The number of Java versions allow finer grain decision making on what is appropriate for an application. With the adoption of containers, applications are bundled with an exact JDK version rather than having to use one from a systems level. The different versions give developers more options. * Incubating features are new libraries added to the JDK. They were offered starting with Java 9 as a way for people to test and offer feedback more rapidly. With Java 12, preview features will be released. Preview features are similar but are core platform and language features. * Shenandoah and ZGC are both low latency garbage collectors. They originally came from different sources. While both garbage collectors are similar, each has different performance characteristics under different workloads. The two garbage collectors represent options available to JVM developers. * Most non-trivial JDK features take more than six months to develop. Longer term side projects like Amber, Loom, Valhalla are where these features are developed prior to being released with a version of the JDK. The projects range from language enhancements to concurrency work.

Java Language Architect Brian Goetz on Java and the JDK