Jargonaut looks pretty interesting. I was on a team once where the lack of a shared glossary really slowed down development of the process. It's easy to make a glossary in a shared document, or as part of a larger project-management application. But the lack of a specific tool used for maintaining a glossary might make it easy to overlook the need for one. I was a teacher working at a school trying to implement a new model of education, so this isn't just about programming teams.

I have no idea if people would pay for this, but I think it could certainly generate a more thoughtful discussion than what I saw on this weekend's post.