> 4. The Challenge of Security: An Open Door to Threats Attacks are possible whether or not source code is available and whether or not the working is collabor

> 4. The Challenge of Security: An Open Door to Threats Attacks are possible whether or not source code is available and whether or not the working is collaborative. FOSS can make such attack easier but will also make fixing it easier, too, so there is an advantage to it as well. > 6. The Documentation Disaster: A Maze with No Map It is true that many FOSS lacks good documentation. However, there are many that do have good documentation (and if something is not clear from the documentation, which I have found to be the case sometimes, the source code is available to try to figure it out from that if necessary; I have used this several times even for software that has been very well documented). For example, TeX, METAFONT, SQLite, and many GNU programs, do have good documentation. With my own programs, I try to document them good too, but even then the source code is available in case that helps too. > 7. The Community Paradox: Too Many Cooks Spoil the Broth True, but there is the difference of "cathedral" and "bazaar" style and projects may be somewhere in between. (For example, SQLite has public source code that anyone can view and can modify for their own use and for redistribution, but the official project will not accept external contributions; they make SQLite entirely by themself instead of by everyone else in the world too. (For another example, I have hardly received any contributions to my own projects at all, but if I do, I might accept them although I would ensure to personally review them first and then make the appropriate changes to the code (whether they are copied from the contribution or rewritten or a bit of both).) > 3.10 Forking Dilemmas: Fragmentation and Confusion Even if it does divide efforts and divide the community, occasionally the authors/maintainers of different forks may work together for some purposes too, which can be helpful too. (For example, I have forked uxnasm, although I still keep track of the changes in the offical version and put those into my version too.) > 3.13 The Invisible Labor: Unpaid and Unacknowledged I do not entirely agree. If the people write the software voluntarily, then they shouldn't care that it may be unpaid and unacknowledged and unappreciated. I write it voluntarily because I don't care that it is unpaid and unacknowledged and unappreciated. It is not unethical. > 3.16 The Talent Gap: A Skilled Labor Shortage There are probably are, but there may also be some programmers who insist to work for free and in their own time. > 3.18 The Dependence Risk: The Hidden Power of OSS The problem of discontinued projects and updates not being released in a timely manner can exist with proprietary software as much as FOSS. However, in the case of FOSS you could maintain it yourself if you want to do (if maintenance is needed), or make your own modifications if they are needed.