|Perl: the Markov chain saw|
> And they all have documents, community, examples, tests, profiling,
This has nothing to do with spoonfeeding. Documentation (and exambles) offer a way to make the (end-)user understand what the module has to offer. If an example is clear and understandable, the possible (new) end-user can take a (quick) decision on the usefulness of the module and if it is going to help solving his/her problem.
The better your examples are, the less errors the user will make, and the less bug reports you get.
From your tone, also in other posts, I however think that you are not interested in bug reports, as your code - d'uh! of course - is without errors and self-explaining. So it doesn't need examples or documentation, as it will solve the problem on it's own. By pure magic. This is what the world was really waiting for.
> and a really noticeable lack of ego about how effing Earth shattering their approach to solving this well-trod problem space is.
That attitude might be what is causing your feelings here. The average monk here thinks that he/she can learn even from the most stupid post or question. By giving an explaining answer, it quite often happens that the poster gets a moment of WOW! which is most likely one of the reasons they post here.
I came here years ago after taking ownership of an abandoned module, just to seek opinions of what other people thought that had to be improved or fixed. Meanwhile I learned that there is much more here that is worth learning about, even if I thought that I already knew all about that.
Questions here make me sometimes re-read my own documentation to see where I was unclear. Sometimes that causes the docs to improve, sometimes I just have to tell the other person to re-read that part of the docs. Eventually examples and docs together make perfect sense.
Enjoy, Have FUN! H.Merijn