Linked by Thom Holwerda on Sun 15th Oct 2006 11:02 UTC, submitted by michuk
Permalink for comment 172029
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2006-08-08
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).