Conversely, if your custom content module just wraps what should be a field, you are going to make me cry.
To some degree, this type of argument is now irrelevant. Newest versions of CCK allow adding of custom fields to /any/ node type, regardless if it's just a wrapper around custom fields. There is no technical limitations for module developers to continue right on making their own custom node types as they have in the past. Instead, we have to convince them with design possibilities or "it's better this way", such as the merging of OG + CCK + Case Tracker in http://drupal.org/node/105808.
Compare the usefulness of an event node type vs. being able to attach event data to any node type (including, but not limited to, an
Yep, bingo. I've recreated the concept of project milestones in Case Tracker using case + cck + event. -- Morbus Iff ( evil is my sour flavor ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus