@mishmich

Comparing the level of polish and breath of documentation in open source projects with that of closed proprietary systems is simply comparing apples with oranges. With open source you get to see the work of the developer/s, including their documentation, if any, as it is born and thruoughout its development, for free. And if you find a way to menetize it you are welcome to. Many have. Some projects are able to produce great documentation, many times quite better than what you normally get with closed source. Others don't seem to ever be able to do so. Of course, for those projects you can always go to the source if needed. That is jut the way it is. Be grateful that someone has actally coded something you can benefit from.

Constructive criticism and bug reports are always appreciated. But if you start going off about how much you prefer the quality of the closed proprietary systems, don't expect a lot of sympathy. You can either go back to your proprietay world, work to improve the quality of the project you are interested, do your own, or pay someone to do it for you. Be real. Do you think that the documentation on the proprietary products appeared magically? Of course not. Someone was paid to produce them. And you had to wait until the developers were ready to show it to you. And you don't get to see the source code. So, advantages and disadvantages, apples and oranges. Please spare us your rants.