ALLENW  Since my bugs got fixed :), I uses this almost daily when I'm feeling too lazy to write LDIF.  
(Version 1.1rc2)

ALLENW  The game choices compared to the PC version aren't very good. It looks like a lot of games are running in some emulation mode, given the number of ancient Atari 2600 games. Given the spyware nature of the GameTap system, it just isn't worth it.  
(Version 3.5)

ALLENW  Unfortunately, the demo doesn't appear to play from a NFS-mounted volume.  
(Version 1.0)

ALLENW  "The game cannot run from a read-only volume."

If I can't put it in /Network and expect it to run everyone, then I'm not interested.  
(Version 1.0.3.1)

ALLENW  Based upon the trial, it appears to have some significant bugs. You'll definitely want it to analyze everything twice. The first time around, it said pretty much everything on the Pixies' "Death to the Pixies" album was 10 BPM on the first pass with an unknown beat intensity. The second time around, songs like "Debaser" came out at a much more believable 135/40. I realize the FAQ says something about a 'corrupted iTunes library', but given that this was a fresh playlist, I'm highly doubtful.]

Additionally, if you have a large library (I gave it over 13,000 tracks to chew on) it overestimates tremendously. It started out at 20 hours and a ten minutes later, it is now down to 8 hours. It'd be nice to have a better estimation. Perhaps it is counting the double analysis that you'll have to do?

I'd recommend anyone interested spend some serious quality time with it. Unfortunately, I'm not sure 24 hours is enough for those with large libraries, much less the 13 hours left as of this posting.  
(Version 1.2.2b)

ALLENW  I really like the app, but it is a bit unusable due to one major bug and one minor one for anyone hoping to use it for critical work:

major: It looks like LDAP Studio doesn't like DN's with / in them. Operations on such DN's results in the queries to the LDAP server failing This makes it particularly hard to use for entries like automountKey=/home, which are very crucial for many deployments.

minor: Clicking on an such an entry throws up an error that says "Error reading entry". Clicking on details shows an LDAP error code 32 - no such object. Rather than show you what LDAP Studio is trying to query, I had to hop onto the server to see what it was looking for. [That's when I discovered the major problem above.]   
(Version 0.8)