@elebertus @mhoye @coder @MaddieM4 I wrote about the topic here:

https://alex.corcoles.net/notes/tech/containers-might-not-be-the-right-answer

It really depends. In any case, I agree that software should be designed to be easy to run. In some cases, containers can be the right answer.

@coder @MaddieM4 @mhoye @elebertus for internal projects, my preferred way is to hope that I only have to support a limited number of environments, and make sure there's up-to-date instructions for all of them. I'm likely lucky, but in the projects I've worked on, this has not been so difficult!

My big issue is with having to support macOS or Windows, because frequently, work will not provide me environments.

@MaddieM4 @elebertus @mhoye I don't know, the problem is that containers bring their own problems to the table.

Yes, in a way it simplifies things because suddenly everyone is on a "single environment". But I find Docker very problematic. Podman is nice, but then some people want to use Docker anyway.

Unfortunately, any answer has its problems. At work we currently use nixpkgs for dependencies, but that also brings its own problems.