Putting make on the Bus

Linux has a software utility that can read a special language, interpreting the language as a 'dependency' tree, which files rely on other files, and the terminals of te tree are actions to take, generally run compiles, links, text processors, set variables in the environment; the actions actually defined in the syntax. The syntax is a brain twisting set of dollar signs mixed with punctuation marks, which select from a set of files.

In the system, all the dependencies have been pushed up a layer, done with Python or Golang.  Make has the ability to find and sift through files, but we also have a bunch of other codes, like Midnight Command, which goes on the Bus sooner or later.   In this system, if make runs the directory tree, it can make API calls to Midnight Commander. Make needs to expose its file handling anyway, as an API.  It is simply, the whole concept is to push dependencies up where powerful syntax engines can manage hundreds, thousands f ad hoc snippets, the collection of which is enterprise level.  We are sitting in make's linux layer.

The make typeface explosion can simply be converted into a set of method identifiers, its sub components exposed.

How about bash scripts?

Absolutely,on the bus. Bash already has a bus protocol, a few lines of code and it works fine on the universal access bus.

bash
{a bunch of bash script
   and you stay in bash until you hit
   cntrl c or bash executes an exit
}

Bash is a natural syntax engine.  We can do that with make, make is a special syntax, but much of its function goes away when something like bash arrives, and bash it programmable by higher level engines.  In fact, most configurations will run bash on the side, a utility available on the bus.  We can do that with make, easy enough.