News for hackers. Stuff that matters.
Re:Engine Yard's sponsorship of RVM is coming to an end by jrochkind1 on Tuesday October 29, 2013 @12:07PM (#6635185)
> There's a bigger dependency management problem where you need to distribute source code to users of tools rather than distributing compiled code.

At first I nodded my head to myself, but after thinking about it, I'm not actually sure that's true.

You can still have dependencies with binary distribution (if using dynamic linking etc). apt, yum, etc, were invented to deal with this right?

And it can still be a nightmare if you have two different things on your system that need different versions of the same dependency -- even a binary dependency. Have you tried to deal with two different binaries that need different versions of libxml? It can be nightmarish.

Re:Engine Yard's sponsorship of RVM is coming to an end by dragonwriter on Tuesday October 29, 2013 @12:10PM (#6635219)
The dependency management issues that come with distributing interpreted source like Ruby are superset of the issues that come with binary distribution.

That's not to say that binary distributions can't also have dependency nightmares.

Re:Engine Yard's sponsorship of RVM is coming to an end by jrochkind1 on Tuesday October 29, 2013 @01:02PM (#6635703)
I'm still suspicious. What's an example of a category of dependency problem that only effects interpreted source and not binary? I can't think of any.

Whether the files on disk are machine code (binary) that will be executed directly by the machine, or some other kind of code that will be executed by an interpreter -- I can't think of any dependency issues effected by that.

Ah, wait I can think of exactly one, issues with depending on a certain version of the interpreter. That's it.