This is old news, but here’s Sun’s explanation for their confusing Java version numbers, I think it is really funny:

Both version numbers “1.5.0″ and “5.0″ are used to identify this release of the Java 2 Platform Standard Edition. Version “5.0″ is the product version, while “1.5.0″ is the developer version. The number “5.0″ is used to better reflect the level of maturity, stability, scalability and security of the J2SE.

The number “5.0″ was arrived at by dropping the leading “1.” from “1.5.0″. Where you might have expected to see 1.5.0, it is now 5.0 (and where it was 1.5, it is now 5).

I’m sure some poor guy was told “here’s our incomprehensible decision, now document it”.

According to this New Scientist article, most scientific papers are probably wrong:

John Ioannidis, an epidemiologist at the University of Ioannina School of Medicine in Greece, says that small sample sizes, poor study design, researcher bias, and selective reporting and other problems combine to make most research findings false.

In my opinion, there is no question that the weak review process most conferences enjoy and the pressure to publish lots of new results, as opposed to verifying what others have done, contribute to this. In my experience, very few people will ever try to reproduce your results, very few people will check your proofs, very few people will reimplement your algorithms.

A few years ago, I tried to publish an errata to one of my paper. It took some doing since the editors had never received such a request. Quite clearly, our tolerance for unaccurate or wrong results is quite high.

Is it a problem? If you are an engineer trying to implement a new system, and you are naïve enough to trust a few scientific papers, then you can get in big trouble. It usually isn’t much of a problem because the average engineer doesn’t read cutting edge scientific papers. It seems obvious that the problem can get more serious if medical doctors read cutting edge articles… do they?

There is exactly one Java application I use routinely, jedit. It is an excellent text editor. As it turns out, the author doesn’t think too highly of Java itself:

I wonder how an extensively hyped piece of software like Java 1.5 — Sun told us it was “the most stable Java release ever” — could be shipped out the door with such critical bugs. Anybody who is still attempting to do client-side development in Java is either retarded, a clueless summer intern working at Sun, or both. This must be why after 8 years of (broken) promises regarding Swing and client-side Java, there are exactly zero Java applications in wide use.

I agree with Slava. Java is a terrible platform for client-side work. Applets died quite some time ago, but now, the remaining client-side applications will live a slow, painful death.

Disclaimer: I still use Java extensively, but not for developing anything that looks like client-side applications. Yet, I seriously worry about Java’s future on the server as well… but this will be for another post…

Paul Graham says that transparency (and thus data recording) is the way out of corruption:

How do you break the connection between wealth and power? Demand transparency. Watch closely how power is exercised, and demand an account of how decisions are made. Why aren’t all police interrogations videotaped? Why did 36% of Princeton’s class of 2007 come from prep schools, when only 1.7% of American kids attend them? Why did the US really invade Iraq? Why don’t government officials disclose more about their finances, and why only during their term of office?

This is very important. Being rich brings you security, but not a lot of power if you have to go through the same process as everyone else. A just society is an open society where we record everything.

Big Brother might actually be the ticket to a just society.

Update: a much simpler approach is described in Embedding fonts for IEEE.

My friend Yuhong reminded me to make sure I embed all fonts in the pdf file for our ICDM-05 paper. This seems to be an IEEE requirement.

Turns out to be a non trivial task, but not difficult. Here’s what I did (applies to a Linux TeTeX 3.0 distribution):

1. As root, type “updmap –edit”, edit the config file so that it has the following content:
   
#pdftexDownloadBase14 false
pdftexDownloadBase14 true
2. Run pdflatex over your document.
3. Run pdffonts over the produced pdf file, all fonts should have true in the columns “emb” and “sub”.

Subscribe to this blog
in a reader
or by Email.