Finally I found the easy way to get the disassembler plugin working on my Linux box - simply follow the instructions at https://github.com/abak/openjdk-hsdis
The aim is to be able to follow the experiments published at https://psy-lob-saw.blogspot.com/ and https://shipilev.net/

Video playback from HTML5 sources such as youtube, vimeo and vessel has been slow and choppy in Firefox, while they all worked well in Chrome (I'm on a slow, old box, the CPU is Core2 Duo, the video card is more recent, nVidia GTX650 with the binary drivers). Finally, I've found that Firefox 37 allowed me to play back everything at good speed and full resolution (1080p) at full screen with the following settings:

Summarising the discussion on darktable-users mailing list (main contributors to the solution were Ulrich Pegelow and Federico Bruni): darktable lost access to OpenCL upon upgrading to Ubuntu 14.04 ('trusty thar') or Linux Mint 17. Here's how to get it up to speed again:

Some older versions of nVidia drivers fail to compile darktable's OpenCL kernels (files that contain the GPU-accelerated image operations). You'll find updated versions here:
https://launchpad.net/~xorg-edgers/+archive/ubuntu/ppa

If you don't like how much screen estate is wasted, and how your eyes grow tired of the glaring white interface, check out the following links:

Or, the road to hell is paved with good intentions.

A colleague of mine was recently writing a unit test. At one point, he wanted to determine what log message the component under test generated. The component was similar to this (source is on GitHub):

I gathered the following information from Spring's documentation (http://static.springsource.org/spring/docs/3.0.x/spring-framework-refer…), the Maven-aspectj plugins's site (http://mojo.codehaus.org/aspectj-maven-plugin/) and the ant task's reference (http://www.eclipse.org/aspectj/doc/next/devguide/antTasks-iajc.html#

According to Visualizing Java Garbage Collection by Ben Evans:

Suppose you have to unit-test some Java code that writes to the console. Here's a way to do it:

Updated: you should check out this 40-minute presentation. The stuff below covers just one of his recommendations: testing code that changes often, in case your VCS is SVN.