Comments on: JavaPolis Disconnected http://www.blog.dannynet.net/archives/29 Pondering Programming and Poetry Fri, 21 Nov 2008 19:54:27 +0000 http://wordpress.org/?v=2.6.3 By: Stephan Janssen http://www.blog.dannynet.net/archives/29#comment-422 Stephan Janssen Tue, 14 Mar 2006 14:34:25 +0000 http://www.blog.dannynet.net/?p=29#comment-422 FYI - The interview with Brian Goetz is now available as a podcast on the JavaPolis wiki site (http://www.javapolis.com) FYI - The interview with Brian Goetz is now available as a podcast on the JavaPolis wiki site (http://www.javapolis.com)

]]> By: Danny’s Blog » Blog Archive » Final Thoughts on JavaPolis 2005, Part 1 http://www.blog.dannynet.net/archives/29#comment-202 Danny’s Blog » Blog Archive » Final Thoughts on JavaPolis 2005, Part 1 Sat, 28 Jan 2006 08:32:52 +0000 http://www.blog.dannynet.net/?p=29#comment-202 [...] Not being able to blog live during JavaPolis 2005 leaves me with several pages filled with scribbled notes on the various presentations. I’m glad that JavaPolis 2006 is said to feature free on-site WiFi access (you read it here first!). But even so, I’m not sure how easy it is to blog live on the spot. My laptop is rather big and heavy to carry around, it always finds a way to play the Windows welcome jingle when it boots up, no matter what settings I tweak, and it’s actually difficult to focus on the presentation and write a cohesive, intelligible blog entry. So, about these notes. Thursday I saw… [...] [...] Not being able to blog live during JavaPolis 2005 leaves me with several pages filled with scribbled notes on the various presentations. I’m glad that JavaPolis 2006 is said to feature free on-site WiFi access (you read it here first!). But even so, I’m not sure how easy it is to blog live on the spot. My laptop is rather big and heavy to carry around, it always finds a way to play the Windows welcome jingle when it boots up, no matter what settings I tweak, and it’s actually difficult to focus on the presentation and write a cohesive, intelligible blog entry. So, about these notes. Thursday I saw… [...]

]]> By: Danny http://www.blog.dannynet.net/archives/29#comment-27 Danny Wed, 21 Dec 2005 22:06:34 +0000 http://www.blog.dannynet.net/?p=29#comment-27 Brian, I don't doubt that the optimization was not trivial. However, from your presentation I got the impression that the core JDK team did not start looking at optimization until after (and because) the concurrency library prooved to perform better. I'm intrigued, by the way, by the notion of testing synchronization. I always learned that almost nothing to do with synchronization is 100% predictable; so how do you test this reliably? How do you reproduce test cases? Brian,
I don’t doubt that the optimization was not trivial. However, from your presentation I got the impression that the core JDK team did not start looking at optimization until after (and because) the concurrency library prooved to perform better.
I’m intrigued, by the way, by the notion of testing synchronization. I always learned that almost nothing to do with synchronization is 100% predictable; so how do you test this reliably? How do you reproduce test cases?

]]> By: Brian Goetz http://www.blog.dannynet.net/archives/29#comment-25 Brian Goetz Wed, 21 Dec 2005 00:22:08 +0000 http://www.blog.dannynet.net/?p=29#comment-25 > I wonder why they waited so long with doing that optimization… It was not a trivial optimization; it involved rewriting a substantial amount of core code in the JVM, and, more time-consuming, TESTING it. Synchronization interacts with everything -- garbage collection, scheduling, JIT compilation. Its not just a matter of flipping a switch. Developer and testing manpower is a limited resource. Its not that the core JDK team didn't know that performance could be improved; its simply a matter of when it comes to the top of the priority list. > I wonder why they waited so long with doing that optimization…

It was not a trivial optimization; it involved rewriting a substantial amount of core code in the JVM, and, more time-consuming, TESTING it. Synchronization interacts with everything — garbage collection, scheduling, JIT compilation. Its not just a matter of flipping a switch.

Developer and testing manpower is a limited resource. Its not that the core JDK team didn’t know that performance could be improved; its simply a matter of when it comes to the top of the priority list.

]]> By: Stephan Janssen http://www.blog.dannynet.net/archives/29#comment-22 Stephan Janssen Sun, 18 Dec 2005 08:54:05 +0000 http://www.blog.dannynet.net/?p=29#comment-22 Next year JavaPolis will provide its own FREE WIFI access instead of counting on the venue provider !! Next year JavaPolis will provide its own FREE WIFI access instead of counting on the venue provider !!

]]>