3 ms·
Containers solve the dependency problem by simply pretending it doesn't exist. I used to do UNIX integration work in the late 1990's early 2000's and container
by AndyMcConachie 6y ago
Containers solve the dependency problem by simply pretending it doesn't exist.
I used to do UNIX integration work in the late 1990's early 2000's and containers weren't really a thing. So you had to make sure libs from one program didn't crap on another program. And developers had to be conscious of what dependencies they included in their code. Nowadays they don't have to care as much because of containers. Every program can have its own dependencies. Thereby solving the integration problem.
A better solution would be to actually integrate programs and their dependencies into working systems, but no one has time for that. Software bloat is fine. Computers are cheap and fast. And actually understanding what we're doing would be too expensive. So just wrap all your have finished crapware up in a giant black box and dump it on a server.
- rileymat2 6y agoWhy is this a better solution? Separating the dependencies between programs allows you to test and release independently to allow incremental upgrades. IMO that is better.
- piaste 6y agoI'm very interested in understanding what I'm doing and what I'm bundling into my software. What I'm not interested in, is this kind of walking uphill in the snow both ways: > So you had to make sure libs from one program didn't crap on another program. And developers had to be conscious of what dependencies they included in their code. ie. having to understand what everybody else is doing in order for my software to run properly. No thanks. That's not why I'm here. I'll put the exact dependencies I want, in the versions which work best for my software, into a Docker image or whatever tool offers a similar level of isolation, and I'll be working on my code while everybody else spends their time fighting over the ABI compatibility of C system libraries.