1) Simple is not simplistic. Sometimes subprocesses are much better than the alternatives, such as threads, as they do not share memory space and cpu scheduling

1) Simple is not simplistic. Sometimes subprocesses are much better than the alternatives, such as threads, as they do not share memory space and cpu scheduling. They force the use of reasonably well defined interfaces in a way nothing else can. (If it is text you have a different self inflicted problem perhaps.) 2) Testing separate processes and coverage testing them is easier than testing and coverage of an interlinked software. 3) Using homegrown interlinked software is not a reason to skimp on devops. Nor is maintaining it cheaper than maintaining third party solutions in principle. (There are special cases.) 4) You sound sour for some reason.