![\"\"](\"http:\/\/1.bp.blogspot.com\/_VliUFo33M5Y\/S_K53a9PJlI\/AAAAAAAAA4A\/GDWPaHv8IEE\/s1600\/IMG_1461.jpg\")
<\/a><\/div>\nGeeCON 2009<\/a> in Cracow was a wonderful experience, and this year<\/a> Poznan held the conference. If you ever wonder whether GeeCON is worth the time and money, the answer is plain and simple: definitely yes.<\/p>\n I’m not able to give you a full review this time, as I’m leaving tomorrow for Paris, and I haven’t prepared myself yet, but let me summarize the most important topics.<\/p>\n There were two different presentations about Erlang way (Actor<\/a> and Agent models) of solving the problem with concurrency. One was a general overview of the problem and possible solutions running on JVM, and the other was about Akka Project\/Platform<\/a> that looks very interesting and above all, is simple to use (at least from what we’ve seen at the presentation). So far I’ve been trying to shield myself from concurrency problems with web servers, stateless services and optimistic locking on database level, but the solution presented here is really appealing. I’d love to try it out.<\/p>\n Joonas Lehtinen had a very nice lecture about Vaadin. There was a talk about Hades<\/a> which is probably going to replace the solution I usually use (hibernate-generic-dao<\/a>). Kuba Kurlenda is testing it on real project right now.<\/p>\n Stephan Herrmann was talking about an evolutionary idea for Object Oriented Programming:\u00a0 Object Teams<\/a>. This may be the next big step we need, but it would have to gain some momentum and find a real life use in a big project. Unfortunately Object Teams do not yet have a successful example to follow. The main question I see is whether it’s worth investing the time of your team, while everyone already knows about design patterns, which solve similar problems.<\/p>\n<\/a><\/div>\n