"Installation: we recommend that you use Docker."

what I'm supposed to see: "hey, it's a simple one-liner! Such clean install, much wow."

what I actually see: "we couldn't figure out how to install this thing on anything but our own machine, but hey, here is a well-compressed image of our entire disk, use this instead so that we can stop trying"


@ssafar Couldn't agree more. Docker is making developers lazy and leading to software that's impossible to install outside of the very specific hand-tweaked environment provided by the docker image.

@dfs @ssafar It's not true all the time, but it definitely can be.

@hhardy01 @dfs @ssafar honestly, your Makefile should allow folding this into just `make install`

@hhardy01 @ssafar Everything I write works that way, although there may be a ./configure step before the first make. (Yes, I do use autotools for some projects.)

@dfs @ssafar

I thought about including ./configure, but I was making a reference to the most ancient, bsdish way I learned I think SunOS 4.1.1.

I'm just making an obscure joke really, though I do get aggravated when package manglers gunna mangle. :)

Between docker and static linking we are going back 30 years in security, maintainability and modularity. Goodbye library updates, goodbye auditing.

@dfs @ssafar sure, but i think that docker was so successful because environment reproducibility was already really bad; it wasn't bad just because of docker

Its not necessary about being lazy but f.e. about being able to install software in repeatable manner regardless of OS/libraries version .
Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.