Skip to main content

Java productivity and the Rails community

I need to write a Java-based web app (it has to be Java because of i18n and scalability issues my employer has with Rails) and I am looking at tools that increase my mileage. Under consideration where Seam and AppFuse, but what made me give Seam a shot is this video:
While I do not need to write a CRUD app this nicely shows how to actually get started without all the plumbing one usually has to do in Java EE (and even then there's some left). Anyway, I'll keep you posted on Seam.

Related to my research on this I came across a thread on the Rails mailing list. For christ's sake! It seems that the converted Java-guys are now Ruby-zealots that now find their pleasure in bashing Java EE. That's a shame because the Ruby community was so well-recognized for being friendly.

PS: if you also need to make up your mind about AppFuse and Seam I found Matt Raible's comments helpful (Matt is the project lead of AppFuse)


Popular posts from this blog

Python script to set genre in iTunes with tags

Now that I have started to seriously use iTunes I figured it might be nice to have the genre tag set in a meaningful way. Since I have a reasonably large collection of mp3s doing that manually was out of question - I wrote me a Python script to do that. There seems to be a large demand for such a functionality (at least I found a lot of questions on how to automatically set the genre tag) so maybe someone else finds the script useful. It is pasted below.

General Strategy

The basic idea is to use's tags for genre tagging. In iTunes the genre tag is IMO best used when it only contains one single genre, i.e. something like "Electronica", not something like "Electronica / Dance". On the other hand dropping all but one tag would lose a lot of information, so I decided to use the groupings tag for additional information that is contained in the list of tags that an artist has on In the example above that would be something like "Electronica, Dance…

mp3tagger on GitHub

On the mp3 tagger post I have received quite a bit of feedback and feature requests. Therefore, I thought it might be a good idea to do "social coding" and put the code on GitHub where it can easily be forked (and the forks can be watched).

Other than that, the latest version of the tagger contains these improvements:
the keys and secret are not stored in the code anymore, but entered on the first run and stored in ~/.mp3tagger.cfgyou can run the script in two additional modes: simulation and ask. In simulation mode no changes to mp3s will be saved, in ask mode you will be asked to save each change. Start the script with flags "-m simulation" or "-m ask", respectively.It is now possible to specify a list of genre tags that will be considered (additionally to the mp3 default genre tags). The list needs to be stored in a config file at ~/.mp3tagger_genres.cfg (in the "generic" section of the file). The full format this file needs to have is …