After writing about my personal experience as a presenter at this year’s Oracle Code One, I was asked for my opinion on what could be done to improve the experience for attendees and presenters in the future. While I have a tiny bit of experience in organizing and running a conference, this year called DawsCon, having 100 attendees is not the same as having 10K+. So here are my thoughts, for better or for worse, on what Oracle’s conference organizers can do in the future.
Let’s begin with the venue. The Moscone Center has over 700,000 square feet of space spread across three buildings. Code One was held in the Moscone West building, which has 300,000 square feet of conference space, such as meeting rooms and exhibition areas, and an additional 75,000 square feet of pre-conference space that effectively means lobby space on each of the three floors. This year, Code One occupied the first floor for its exhibition space and the second floor for conference sessions. The third floor was used by Oracle Open World. In addition, the basement of the Moscone North building, where a large presentation space exists, was used for keynotes. The remaining space in the North and South buildings were used by the Oracle Open World conference with its 40K+ attendees. The South building was torn down about two years ago and its reconstruction is almost complete.
The press release "Oracle Code One Java Keynote Outlines the Future of Java" describes the Java Keynote at Oracle Code "highlight[ing] future projects:" Project Valhalla, Project Panama, Project Amber, and Project Loom. This post provides brief summaries of each of these projects and some recent work associated with each of these projects for those who may not be familiar.
Project Panama is about "Interconnecting JVM and native code." Its introduction states, "We are improving and enriching the connections between the Java TM virtual machine and well-defined but ‘foreign’ (non-Java) APIs, including many interfaces commonly used by C programmers."