@Stellar@mk.absturztau.be the reason devs like docker is that it makes it orders of magnitude easier for the dev to support every single linux distro and library combo (which users insist on), and you don't have to spend hours and hours of your completely unpaid time to find out why the specific build of glibc on debian 7.2 breaks your app or something
this is a really common scenario, it's why docker and containers in general exist at all
@Stellar@mk.absturztau.be it is gross but to be fair most software assumes you're running it on a shared host, things like lxc aren't used by that many people
i can tell you i stopped supporting "build from source" on my biggest 2-year project and now only offer nix and docker builds because it became such a burden to support from-source builds that it was better to just drop it
@Stellar@mk.absturztau.be that's literally untrue though, docker doesn't eat any resources, it's not a VM
processes spawned via docker use exactly the same amount of memory than non-docker things because containers are just standard processes with strict isolation rules
@jessew@Stellar Fun fact: if you forward a docker container port to localhost and then access that port it’ll route all connections through a userspace proxy written in Go. This proxy that just blindly forwards raw data is less efficient than fucking Forgejo.