5 ms·
That's the same for "wget|sh", apt-get, npm or any other system. Now, if the argument is that configure tends to break more often and for more obscure reasons,
by Jare 12y ago
That's the same for "wget|sh", apt-get, npm or any other system. Now, if the argument is that configure tends to break more often and for more obscure reasons, I can tentatively agree with that.
- deong 12y agoThis is the reason why all these standalone things bundle everything into their installation process. The problem is installing 206 different pythons on my system just makes it more likely that something else is going to break.
- garthk 12y ago… which is one of the pressures driving Docker adoption. Each process tree gets its own root filesystem to trash with its multitude of dependencies. DLL hell, shared library hell, JDK hell, Ruby and Python environment hell… a lot of it can be summed up as "userland hell". Docker makes it easy to give the process its own bloody userland and be done with it.
- deong 12y agoI think this falls under the heading of "I'm old", but I already have one machine to maintain. Replacing it with N machines to maintain doesn't feel like a win to me.
- lmm 12y agoI'd actually disagree with that. Auto* breaks less often than wget or npm, IME.