> OS upgrades, deprecations, maintenance are a thing that makes your binary stop working all of a sudden. Good thing I deploy with Docker/Kubernetes and I have

> OS upgrades, deprecations, maintenance are a thing that makes your binary stop working all of a sudden. Good thing I deploy with Docker/Kubernetes and I have a CI/CD pipeline that will warn me about such cases. > It's like choosing prolog in production, finding out that there is no libraries for it and then hacking together Go binary together with it. Hence this thread. Erlang/Elixir brings so much to the table when it comes to distributed computing. Kubernetes + Elixir + libcluster + horde, I don't know any other language that gets better than this. And yet, there are still some librairies I would need, that I don't want to implement myself, because I don't trust myself to implement them properly (see other comments where I talk about iCalendar). So yeah, I need a "hack", and it makes sense to me to delegate the complexity wherever I can. You could argue that I need to create a microservice, and make an HTTP call. But why make an HTTP call when I can just call the binary without the network layer in between?