Right, but the choice is actually "Being able to hire to solve a problem" or "Being required to upskill any developer to become productive", and most would (rightly) choose the former.

> I'd happily program in Brainfuck if that's what it took to avoid Kube.

Why though? Why hate k8s so much that you would choose an unreadable language?

I don't think anyone actually uses Brainfuck. They were being sarcastic.

I was, but the deeper point really is the tradeoff between code complexity and operational complexity. And I'll choose code complexity every time since it occurs early in the process and is less likely to blow up in my customer's faces.

But then it's the runtime what is solving the problem for you, not exactly the language.

Erlang is completely tied to its runtime. Making a distinction is not really important. The point is Erlang gives you the best parts of much more complex solutions in a simple easy to use package.

Agreed, it's kind of a pedantic/moot observation.

Thats even better! That way, you get to program with much saner assumptions in a more pleasant environment, rather than having to write code to smooth that over manually, or deal with configuration and operational hell to make it work at a deployment level.