"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"
@kristof yeah, if it's a complex install, having a Dockerfile is a lot better than not having one; at least you now have _one_ way this thing can be seen working. It's also great for reproducible builds... but if the default way of installing something on your OS involves installing another OS, something might be wrong with our idea of what an OS is supposed to be :)
(I've seen projects where "non-docker" installs were in the "compiling / hacking / advanced" section...)
@ssafar I’d say a “non-docker” install could be reasonably considered “compiling / hacking / advanced” from the project’s standpoint — if I wanted to install something “natively”, but not compile it / hack on it, I’d turn to the distro I use, and not necessarily towards the upstream.
Of course, an OS where Docker is the only way to install something is probably bad (unless you consider Kubernetes an OS… ugh ), but upstream projects are likely not part of any particular OS. Linking to OS packages would still be nice, though.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.