Devoxx 2010: Day 1

First day of Devoxx 2010 was yesterday. It started off really well, because I got the NetBeans Platform lab out of the way within the first 3 hours. It went pretty well, several hardcore NetBeans dream team members were also there, Sven, Florian, Toni, Martin. They did a section at the end called "Advanced Random Stuff", which included slowness detection (Florian will publish a blog entry about this soon, I have the related code and some other tips from him about integrating the Profiler`into your own application on the NetBeans Platform) and a mash-up application by Sven, including Groovy and Scala (i.e., a TopComponent in Groovy and a TopComponent in Scala). He's going to be showing this off at JavaOne Brazil.

There were not too many people attending the lab, but all of them were serious about their interest in the NetBeans Platform, one of them briefly showed me his NetBeans Platform application and I've been trying to find him ever since then... for a screenshot and interview, etc...

I then attended Guillaume's Groovy session, at least, the first two hours. It is great to see the Groovy ecosystem is quite large and diverse. I wonder, though, what proponents of scripting languages such as Groovy (the best of the lot, from a Java point of view) feel about "the fact" (quotes because it's not a fact but my opinion) that they're not pushing Java off the throne, which is what I thought they were aiming at, but that they're (especially Groovy) glue languages. If you look at Groovy as a glue language, then you're never going to be disappointed. But if you see it as a potential replacement for Java, you're in a whole different discussion. I simply don't see large business applications (except for those using Grails) moving to Groovy as their programming language, especially not large business applications (e.g., banks, defence, oil, etc). However, I do see the applicability of Groovy as a key glue language in all these sectors.

After that, I saw a session on Mylyn and one on JCite, which I had never heard of before, which is really interesting for synchronizing code in tutorials with JUnit tests (this combination, but without JCite, is what Jaroslav Tulach used too for his API design book, to ensure that the code samples compiled and worked as expected). Definitely something to investigate.

I attended the Groovy/Grails BOF in the evening and then a very interesting one by Heinz Kabutz on, where he introduced an annotation for stating the intention to use a particular pattern. The discussion centered on what one could do with that annotation, e.g., create a tool to verify whether the pattern has been used, but how to identify that usage? Or maybe as a way for newbies to a project to understand the intention of the code, i.e., by looking at the annotations. Very interesting, anyway, regardless of what you think about patterns. (By the way, Heinz stated that he considers JDeveloper to have the best tooling for UML, i.e., better than any other UML tool, regardless of free or open source or whatever.)

The day ended with a long drinking session with CollectionSpy (sounds like a very interesting Java profiler tool), Heinz, Paris (Greek JUG leader), Sven, Florian, Martin, and others.


>> one of them briefly showed me his NetBeans Platform application and I've been trying to find him ever since then

Oh, look at


Posted by Hartmut on November 24, 2010 at 02:18 PM PST #

Hi Hartmut, that's great to hear from you! Can you drop me an e-mail at geertjan dot wielenga at oracle dot com, with a few screenshots and a description of the application?

Posted by Geertjan Wielenga on November 24, 2010 at 03:41 PM PST #

Post a Comment:
  • HTML Syntax: NOT allowed

Geertjan Wielenga (@geertjanw) is a Principal Product Manager in the Oracle Developer Tools group living & working in Amsterdam. He is a Java technology enthusiast, evangelist, trainer, speaker, and writer. He blogs here daily.

The focus of this blog is mostly on NetBeans (a development tool primarily for Java programmers), with an occasional reference to NetBeans, and sometimes diverging to topics relating to NetBeans. And then there are days when NetBeans is mentioned, just for a change.


« June 2016