I consider that a good thing. Do you prefer terse man pages to the loquacious documentation provided for .NET?
I do find man pages and the docs in /usr/share/doc usually answer my questions. I have had to hunt for answers that I felt could have been better documented, but usually I just want to know what parameter types a function takes or returns or something else simple like that.
You don't think, even for a second, that 1G of text/html might be too much? Somtimes it seemed like nearly all of the MSKB was included too, I would stumble upon docs totally unrelated to what I was looking for and sometimes onto docs that didn't even seem related to development at all. And I found their help search to be less than good at it's job, but that's another topic.
Providing explanations of the functions and all the data types that go in and out of them is good.
Providing examples to better show what the function can and and can't do is good.
Providing explanations of caveats and the 'correct' way to do things is good.
Providing docs on things unrelated, like Exchange migration, seems pointless. It's been a while but I swear I ran into this paper on the .Net docs quite often and it was never even related to what I wanted.
I won't arge that more is worse than less in the doc dept, and I'm not a paid win32 programmer, but I think the .Net docs could have been smaller.
Facebook
Twitter