| |||||||||||||
A couple of lessons on the hazards of proprietary softwareA couple of lessons on the hazards of proprietary softwarePosted Aug 14, 2006 21:04 UTC (Mon) by leoc (subscriber, #39773)In reply to: A couple of lessons on the hazards of proprietary software by dlang Parent article: A couple of lessons on the hazards of proprietary software
Obscurity through complexity is NOT the same thing as obscurity through secrecy. So long as you have access to the source code to the version of the GIMP you are using, then you have a 100% accurate set of "documentation" on how to load and manipulate the data. Yes, you could lose the source to the version you are using, but then all your hard drives and backups could gte destroyed in a fire, too. Storing information in digital form is fundamentally risky, and losing the source code to a critical peice of infrastructure is something you can screw up, but noone can walk into your place of business and TAKE the source code from you. With closed source software, they can. That's the point.
(Log in to post comments)
|
|||||||||||||