Linked by Thom Holwerda on Sun 15th Oct 2006 11:02 UTC, submitted by michuk
GNU, GPL, Open Source "There is one huge difference between the free and non-free software that has some very practical implications in the way we use it. One of those implications are the dependencies between single software packages in the free software model. What do they have to do with the free software philosophy and why should not you be afraid of them? Read on to find this out."
Permalink for comment 172029
To read all comments associated with this story, please click here.
Member since:

Do non-free software use libraries.
Yes, all the time.

Does free software use external libraries
Yes, all the time.

Sure, I agree.

My point was (at least one of my points) that the OSS libraries are usually independent and usable by everyone. They are installed as independent packages in the system as well (just like GTK framework in Windows) which makes them easy to manage (update, uninstall, replace, etc).

Closed-source dependencies are usually bundled with the proprietary the software so you don't really care whether they are external dependencies or just part of the software.

But you are right -- I probably could have made the points better in the article. The main idea was just to describe the way the software is crated in general and explain the reasons for the so called "dependency hell" some Linux users might experience (but it's also mostly a relict of the past now).

Reply Score: 1