<<< Previous speaker Next speaker >>>

Brian Goetz, Sun Microsystems

 Brian  Goetz

Brian Goetz has been a professional software developer for 20 years. He is the author of over 75 articles on software development, and his book, Java Concurrency In Practice, was published in May 2006 by Addison-Wesley.

He serves on the JCP Expert Groups for JSRs 166 (concurrency utilities), 107 (caching), and 305 (annotations for safety analysis).

He is a frequent presenter at JavaOne, OOPSLA, JavaPolis, SDWest, and the No Fluff Just Stuff Software Symposium Tour. Brian is a Sr. Staff Engineer at Sun Microsystems.

Presentation: "Introduction: Evolving Java"

Track:   Evolving Java

Time: Thursday 10:30 - 10:45

Location: St James's Suite

Abstract: From its initial vision for mobile code and interactive web pages, the Java platform has come a long way in twelve years! Java now runs on platforms ranging from enterprise-grade servers to mobile phones and smart cards. If you poll developers, every one of them has an idea to make the Java language "better" or to extend the range of environments in which Java can be deployed. This drive for change is balanced by a large number of customers who like Java just fine as it is. How do you evolve a widely-used, mature language and platform? Come hear experts from the Java community discuss how the Java language and VM are evolving to meet the community's ever-changing needs.

Presentation: "Concurrency, past and present"

Track:   Evolving Java

Time: Thursday 11:00 - 12:00

Location: St James's Suite

Abstract:

With the widespread availability of cheap multi-core processors, concurrency is more important than ever for utilizing the hardware resources available to an application.

However, writing safe and performant concurrent code is difficult, and requires a more rigorous design, development, and testing approach in order to produce reliable results.

In this presentation, we'll look at several programming models for concurrency, contrast them with the shared-state model that is dominant today, and draw some lessons that can help us write better concurrent programs in Java.