absolutely agree. It seems as if the author is saying all open source, versus the small set of proprietary software. I know I have lots of 'open source' half f

absolutely agree. It seems as if the author is saying all open source, versus the small set of proprietary software. I know I have lots of 'open source' half finished projects, which I may or may not be using, and it doesn't really matter to me if someone else wants to take the code and continue it, or fork it or what have you. I certainly prefer for my web server an open source stack. That's not to say there is anything wrong with proprietary alternatives, but I worked for a very large company that transitioned from proprietary software to open source, precisely for the 'open source' credo (it's stable, tested, more secure etc) as well as its gigantic cost savings annually. I think proprietary software has a place, but I would like to see the author argue when and what those cases are instead of just talking shit on free software. Perhaps desktop applications for MacOSX and Windows is such a case...