Skip to main content

Jazoon 2007: Last day

I didn't really get around to take any notes the last day. Or well, I did take some notes but I lost them.. Here's what I attended at least:
In the last talk, I asked the speaker whether he thought extensions of Java as a platform was a fair way of increasing complexity vs new languages better fit for the job (a more powerful platform does reduce the need for new components), with a particular regard to AOP and Closures. He answered that AspectJ in runtime would be considered a foreign component increasing complexity quite a bit, but closures would be more of a welcome addition to the language.

I asked the same question to Peter Sommerlad yesterday, and his answer was that he discussed this with Kiczales about this some ten years ago, and his belief was that the developers/tools weren't ready for it yet. We first have to master the art of OOP before we advance to AOP, but I'm not sure I agree. Alot of the GoF-patterns we use today are there because of restrictions in C++/Java, and maybe OO wouldn't be that much worse of having to be learned with AOP.. Just a thought.

(By the way, reason this post is done so many days after Jazoon is that we've been constantly occupied since, attending an internal AOP-workshop for the last two days straight. Thanks, Kaare! Great workshop.)

In the closing session/lightning talks I learned how to present the Semantic Web in 1 minute, some good books to read on python and management, and learned lots of other interesting facts that I have since forgotten.

To summarize my experiences of the first Jazoon:

Bad things:
  • Far from packed (700 people I think, was room for a bit more than that methinks)
  • Level of speakers were a bit up'n'down
  • Should've turned the lights in the theaters on during talks
  • The talks' slides (and hopefully video) aren't up yet
  • Zurich is *nearly* as expensive as Oslo. And pretty similar in every other aspect except the language :)
Good things about Jazoon:
  • Attracted a great score of central/south/eastern-European developers (where I predict great things will come from the next few years)
  • Organization was like clock-work
  • Wireless was constantly up
  • Lots of room :)
  • Power slots every other row in the theaters
Thanks to the Jazoon organizers. I really believe you have the infrastructure and organization to become a great conference in the future, perhaps already next year. So get your abstracts ready, folks :)

Oh, and as a side-note, my abstract didn't get accepted for JavaZone this year, so the material probably won't get any more "exposure" here in the blog, although I will continue implementing the pattern in my day-to-day work.

Comments

  1. Dear Thomas, thank you very much for your kind and helpful feedback. Jazoon'07 had just over 800 participants and yes, there was space for more. How did you like the venue? If the venue will be the same for next year then at least we have some spare capacity for more participants :)
    Prepare your abstract for Jazoon'08 now and get ready! Chris (christian.frei@keynode.biz, the organizer of Jazoon'07)

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant...

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password...

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org  - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config...