I think this goes in this forum...
I know there is nothing developers and supporters loath more than a hacker (having been in the software industry) but hey this is open source so:
I have about eight entities that I want to maintain on Drupal. They are called "process" "practice" "domain" "role" etc... they mean something to my users ;-) I want the public to be able to contribute text for them and it be subject to comment etc. So the very best place for them is for each to be a node type.
i tried flexinode and decided not to use it. I'm nervous about the performance impact, i didn't need all the field types (this is basically a technical-book creation system - I mostly just capture a body of text), and I don't like that the node type is cryptic.
i tried using taxonomy. in fact the eight classes are of course in the taxonomy, but using pages for everything and tagging with terms just wasn't working for me. Too confusing to general-public-users to create content/page then select the right taxonomy type. I want create content to be obvious.
So I took the story.module, saved it as process.module, did a global change from story to process, tweeked the help text a bit and tried it. beautiful. if all you want is a basic entity then i'd recommend to anyone forget flexinode and just clone story.module. But that is not the point of my yarn....
then i got to thinking about eight extra modules and the overhead of that. and only two of the entities are actively contributed by the general community. the other six are parent classification hierarchy entities that i can add and they'll stay mostly static.