framiere

Thanks for the paper, it was a nice read. I was stunned to see how straightforward it was.

Basically by order of appearance you look for

* well know files, or registry keys

* patterns in a memory dump

* use a great hack called "the red pill" using the SIDT instruction

* vm specific hardwares

* specific instructions/capabilities

We also use it to apologize when being rude without meaning it.

Example :

you make a remark without really thinking of it because of your professional habits (ex: you should be doing things that way, or going straight to limit-cases or counter-examples) that would made sense in a professional context, but that is not acceptable outside.

You would apologize saying "I am sorry, it is a déformation professionelle"

As a frenchman, I use it from time to time. However I never heard it in the US, is this saying somewhat known/used ?

You are correct, I was pointing to cliff click's blog as he his giving back to the community.

Look at http://blogs.azulsystems.com/cliff/2007/03/a_nonblocking_h.h... : an implementation of a non blocking hashmap without lock that scales beautifully on a bunch of cores without the need of their hardware (http://sourceforge.net/projects/high-scale-lib)

As per actor on the JVM open source projects are blooming around such as http://code.google.com/p/actorom/.

Alex Miller did a nice review here of the solutions out there: http://www.javaworld.com/javaworld/jw-03-2009/jw-03-actor-co...

That is untrue.

Check http://blogs.azulsystems.com/cliff/ for really impressive work on jvm that works on 800+ cores ... oh yes, and you have constant time garbage collection.

You would do a remake of "snake on a plane" with your 100ml ?

http://www.break.com/index/burning-mercury-experiment.html

It reminds me of http://www.agitar.com for the java platform.

It is a very useful approach to prevent regressions while working on legacy code.

Alberto Savoya (who is behind agitar) has a nice definition of legacy code : code that has no unit-test.