Live data from Hacker News

A nice picture of (dependency) hell

disfunksioneel.blogspot.com

11–20 of 25 posts

Re: A nice picture of (dependency) hell

#11
post #9
post #7

Earlier quoted context omitted.

Exactly. This is code reuse done properly, not "dependency hell".

The graph was partially motivated by the experience of compiling a few open source projects in windows. In Gentoo it's not "dependency hell".

Why didn't you call it something non-controversial like "A visualisation of open-source software dependencies" instead of "A nice picture of (dependency) hell", then?

Re: A nice picture of (dependency) hell

#12
post #11
post #9

Earlier quoted context omitted.

The graph was partially motivated by the experience of compiling a few open source projects in windows. In Gentoo it's not "dependency hell".

Why didn't you call it something non-controversial like "A visualisation of open-source software dependencies" instead of "A nice picture of (dependency) hell" , then?

The obvious answer is that the former would not generate nearly so much interest/clicks/attention.

Re: A nice picture of (dependency) hell

#13
post #11
post #9

Earlier quoted context omitted.

The graph was partially motivated by the experience of compiling a few open source projects in windows. In Gentoo it's not "dependency hell".

Why didn't you call it something non-controversial like "A visualisation of open-source software dependencies" instead of "A nice picture of (dependency) hell" , then?

Sensationalism? If you would like a post with a less controversial name, have a look at "High resolution dependency graph".

Sorry if you felt cheated by the title :)

Re: A nice picture of (dependency) hell

#14

I'm not sure what the problem is here. Looks like there's a large, very functional, set of systems that have a lot of reuse. Would it be better if there wasn't the reuse? Or if the system was less functional?

It is a dependency hell, ready to fire at the moment one of the packages changes its interface (API, behaviour, file layout, ...) recursively breaking a fraction of its dependents. Then you end up with multiple versions of the same package, versioned libraries, private copies of libraries and tools, and so on.

Reuse works great on a small scale, but otherwise requires a lot of discipline both from the provider (who must refrain from interface changes, or have support for multiple versions from day one), and the consumer (who should be very considerate on which packages and features he uses).

Re: A nice picture of (dependency) hell

#16
This could be interesting, but there is too much noise and not enough signal. All I can see is a large multicoloured circle. Why not try to process it a bit more so that this could teach us something?

Re: A nice picture of (dependency) hell

#17
post #8

Meanwhile, over in Windows land, I'm trying to remember when I last encountered DLL hell. It's a long time ago now. People simply stopped trying to install DLLs in the system directories and just ship all their dependencies. With the amount of RAM available now, it doesn't matter if you load 100 different versions of a shared library, you're not gonna notice the difference anyway.

In my opinion, that's the very definition of dependency hell - when the system is so badly designed, software is forced to bundle everything and never share it.

That's the reverse of the classic description.

Re: A nice picture of (dependency) hell

#18

Meanwhile, over in Windows land, I'm trying to remember when I last encountered DLL hell. It's a long time ago now. People simply stopped trying to install DLLs in the system directories and just ship all their dependencies. With the amount of RAM available now, it doesn't matter if you load 100 different versions of a shared library, you're not gonna notice the difference anyway.

What happens when someone finds a buffer overflow in that library? In Linux land only one file needs to be updated.

Re: A nice picture of (dependency) hell

#19
post #15
post #9

Earlier quoted context omitted.

The graph was partially motivated by the experience of compiling a few open source projects in windows. In Gentoo it's not "dependency hell".

[deleted]

Forgot password of first account. Coming up and remembering passwords are equally hard

Re: A nice picture of (dependency) hell

#20
post #16

This could be interesting, but there is too much noise and not enough signal. All I can see is a large multicoloured circle. Why not try to process it a bit more so that this could teach us something?

I agree. The graph on the site is already processed a bit, but not enough.

Can you make any suggestions as to how I can make it better?

Post reply on HN