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.

Popular posts from this blog

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 and sa…

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-zsh.git
    -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

I discovere…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…

The Best Log Viewer Ever

This is what it looks like when I want to have a look through the logfile, to see what a user did on one of our machines one day:


Read the whole story about how it works on the Viaboxx Systems blog (and upvote on DZone!).

Microsoft ups their Git efforts another notch

This week Microsoft announced first class Git support embedded in the coming version of Visual Studio.

Now, it's not completely shocking. We could have seen it coming since Microsoft started offering Git repos on CodePlex, and more recently offering a Git client for TFS. In any case, these are some big news. Scott Hanselman weighs on some features and some more background here.

For those who are a bit unaware of what the Git situation on Windows looks like these days, I've dotted down these notes:
Some explanation on these:

msysGit has long been The Way to use Git on Windows. It's basically a port of Git itself, so it's a command-line tool.GitExtensions (includes Visual Studio integration), TortoiseGit, Git Shell, posh-git and most other tools are powered by msysGit.libgit2 is a native library for doing Git stuff. It is developed completely separate from Git itself. The above tools could (and should) probably use libgit2 instead of hooking onto and around msysGit.Github…