I think it makes some good points about the "buy versus FTP" methods of procuring software to support your needs, whether you are a person or an organization.

The way I've usually described it is like this:

If you use open-source software, you own your shop. You have control over the foundation of your business processes.
If you buy closed-source software, you pay someone to own your shop. You give someone a chunk of your revenue, and in the same transaction grant them the authority to steer, control, and sell to your competitors your most intimate internal business processes -- the procedures and algorithms which store, process, and move the data that is the nervous system of your organization; which directly determine the productivity of your organization's members; and which are major factors in the quality and cost of your product.

The only excuse for the latter behavior is time -- time to market. But, and I think this is the bedrock of the open source movement's future, eventually the closed-source internal processes will hang like a dead albatross around the neck of any organization which uses closed- source code for anything other than a stopgap.

Those who do not see closed-source solutions as "temporary", as necessary evils, and who do not implement a policy to shed them continually, will not survive. Their competitors will make sure of it.