POJOs Gone Wild and the 2nd Law of Thermoblogs

A reminder and a few random notes:

POJOs Gone Wild

The "Win a Sticker" contest ends on June 29! Enter today... Remember, international readers, that CodeToJoy pays shipping.

Captain Neato, Twenty Thousand Bytecodes under the Sea

Here is a neat Java Powered Submarine.

Rumor has it that the team tried the software in C++, but the sub sank due to memory leaks. (not really)

Then they tried it with Scheme, but the sub kept lisping at 20 degrees to starboard.

This might be fun. Share your ideas why they couldn't use Ruby, JavaFX, etc...

The 2nd law of Thermoblogs: Entropy == Flame wars

This law of the Net is entirely isomorphic to the Second Law of Thermodynamics. Simply perform these substitutions:

• the "system" and "process" becomes the "blog" (or "post")
  
• "entropy" becomes the "flame war" (or "flames")
  

e.g. 1. To paraphrase Clausius:

The flames of a blog post not in equilibrium will tend to increase over time, approaching a maximum value at equilibrium.

e.g. 2. To paraphrase Bazarov:

The law of existence of flame wars in every blog and of its never decreasing in isolated blogs for any posts whatsoever.

As illustrated on Cafe Au Lait via the "initially interesting yet doomed to thermal death" post on Checked Exceptions