Re^2: Our documentation sucks

I just knew you were going to use me as an example (even though I don't see how it has anything to do with documentation): Should I just print my own HTTP headers?

There are 30+ replies to my thread, including 4 from you. There are around 5 that attempt to answer the original question, with the rest just pointing out that it's a stupid question or using bizarre hypothetical situations to demonstrate its uselessness.

This thread now has more relevant discussion to my question than that one though, so I guess I should be thanking you. I just wonder why you decided not to mention headers at all in that thread and instead went on a tangent about benchmarking.

Comment on Re^2: Our documentation sucks

Replies are listed 'Best First'.
Re^3: Our documentation sucks by chromatic (Archbishop) on Apr 13, 2007 at 06:03 UTC
I just knew you were going to use me as an example (even though I don't see how it has anything to do with documentation)... That's because I don't think the reason people avoid modules is because of poor documentation. CGI.pm has reasonably good documentation. (I say "reasonably" because it has a lot of documentation, and it's really difficult to arrange that in a perfectly clear and obvious way.) I just wonder why you decided not to mention headers at all in that thread and instead went on a tangent about benchmarking. I didn't think you cared about correctness, merely "wastefulness". Update: I don't mean to sound offense, and I realize this can come across that way. I apologize. What I meant to say was that by the point in the conversation where I started, it sounded like the conversation had already gone off on a tangent and you believed that the best reason not to use a module was due to its weight. In my experience, that's rarely a wise choice, especially with regard to network programming.	[reply]

Replies are listed 'Best First'.

Re^3: Our documentation sucks
by chromatic (Archbishop) on Apr 13, 2007 at 06:03 UTC

I just knew you were going to use me as an example (even though I don't see how it has anything to do with documentation)...

That's because I don't think the reason people avoid modules is because of poor documentation. CGI.pm has reasonably good documentation. (I say "reasonably" because it has a lot of documentation, and it's really difficult to arrange that in a perfectly clear and obvious way.)

I just wonder why you decided not to mention headers at all in that thread and instead went on a tangent about benchmarking.

I didn't think you cared about correctness, merely "wastefulness".

Update: I don't mean to sound offense, and I realize this can come across that way. I apologize. What I meant to say was that by the point in the conversation where I started, it sounded like the conversation had already gone off on a tangent and you believed that the best reason not to use a module was due to its weight. In my experience, that's rarely a wise choice, especially with regard to network programming.

[reply]