recursion

Hibernate looks like a really nice persistence framework for Java. It takes the grunt work out of the OO-Relational mapping (at Ancept, we all this the "relay" layer) while still giving you control over the database schema. Plus, unlike some other solutions for this I've seen, it has great documentation. It's amazing what a difference that makes for me in wanting to try something out (and I'm guilty as well -- Eikon has zero docs and no mailing list).

I'm going to see how it works with PostgreSQL.

My boss loves EJB and it's container-managed persistience, but I'm interested in the more light-weight approach of Hibernate. EJB's learning curve is so steep, I'm afraid to touch it, especially for the simple stuff I've got in mind.

Java Persistence Resources:

Java Persistence Engine (Object-Relational Mapping) by Julian Harris.

Object Relational Mapping Tools by Anthony Berglas.

Announcing Hibernate 1.0 Open Source O/R Persistence Tool by Gavin King plus discussion on The Server Side which includes a number of the criticisms of O-R mappers. It's a little old and it seems that Hibernate has fixed a lot of the criticism.

survey of O/R tools thread on jug-discuss mailinglist.

Torque another approach to O-R mapping, from the Jakarta Project. If anyone is aware of of comparison of Hibernate and Torque, please let me know.

ObJect Relational Bridge also from Jakarta. This implements JDO. I think.

Daypop has added 3,000 new sites to its index...but I'm still not in it.

Sigh. I've been trying to get into Daypop for a while, because the world deserves to know what I'm saying! This shit is golden.

Ahem.

I guess I'll try again in a few days. Maybe I just haven't been spidered yet.

I thought this was pretty funny: Dilbert tries extreme programming. There's three strips.

Zoe is the first piece of software I've seen released under a Creative Commons license. It's under the Attribution-NonCommercial License.

Ugh. This is not good. A number of people have criticized the CC licenses because "We don't need any more open source licenses!" but the Creative Commons licenses were never intended to be used for software:

We want to complement, rather than compete with, these existing efforts to ease online sharing and collaboration. Right now we don't plan to get involved in software licensing at all. Instead, we'll concentrate on scholarship, film, literature, music, photography, and other kinds of creative works.

Now some software developers are making the complaint true.

I think there are three types of open source licenses you should use:

1. GPL/LGPL -- when you want to ensure your software always remains Free
2. Apache -- when you want credit
3. BSD/MIT -- when you don't care what people use your software for

Using other licenses or creating your own -- in most cases -- just creates confusion and prevents other people from utilizing your code.