Eclipse TPTP is a waste of time

I wasted many hours of my precious weekend to get the Eclipse TPTP Profiler to work. My scenario was a simple standalone Java application.

Conclusion: it's not worth it, trying TFTP to work is an extremely frustrating experience. My life's too short for this kind of thing and I'm not the only one.

Android API: Can't touch this!

From Ed Burnette's blog entry on the Android SDK M5 update:

But my favorite addition to M5 has to be a function called “getDataFilePath()”. The documentation says:

DO NOT USE THIS FUNCTION!! Someone added this, and they shouldn’t have. You do not have direct access to files inside of a content provider. Don’t touch this. Go away.

MapReduce: is it really "a step backwards"?

Some database people are not too happy about MapReduce starting to win the hearts and minds in academia.

The rhetoric smells like yet another religious war. This is where I spit my morning beverage on the keyboard:

Given the experimental evaluations to date, we have serious doubts about how well MapReduce applications can scale.

Furthermore it seems like they ignore that MapReduce tries to solve a very different problem than an RDBMS. One, for which a traditional DBMS doesn't provide a good solution right now.

MapReduce: A major step backwards by David J. DeWitt and Michael Stonebraker


via Artima.com

The Java closures controversy

Although I didn't have time yet to study all the alternatives in detail, I've read a few blog posts and watched the video of Joshua Bloch's presentation at Javapolis about the BGGA Closures proposal.

I tend to agree with him. Rushing into a closures implementation and adding yet more complexity to Java is a great chance for the Java community to shoot itself in the foot and turning Java into another C++. In my opinion one strength of Java has always been the ability to say no to new features until there was a convincing solution.