This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new!

FUD, to a point

Posted by: Anonymous Coward on August 30, 2006 03:41 AM
I happen to agree that moving to OSS is a prefered move, but there isn't always a project that fits the needs of the business.

Commercial software is usually sold in two ways: perpetual license (with annual maintenance fees), or on a subscription basis (monnthly, yearly, whatever). Both types come with a contract that cannot be unilaterally changed, which leaves me with several possibilities here.

1. The license for the software had expired, or the maintenance fee wasn't paid.
2. The version in question had been EOLed, and no one did anything to upgrade until this emergency presented itself.
3. The language of the contract actually allowed the vendor to screw its customer over.
4. The vendor took it upon itself to screw the customer over outside of the contractual bounds.

I'm sorry, but every single one of those falls into a "vendor management" category, something that small to mid-sized shops have to do regardless of whether the software they're running is open source.

If you want to pick a reason that proprietary software is bad, you're going to have to find a reason other than "I was too busy to manage my vendor relationships."


Return to Why proprietary software is dangerous for business-critical applications