Software emerged from the continued use of the Turing paradigm and allowed us to reuse the electronics. That tactic was very necessary in the days when power- and space-hungry vacuum tubes were the leading electronic devices. No longer is that a factor when we have millions and perhaps billions of transistors on a chip. It is now quite possible to jettison the shared-resource bottleneck by dedicating hardware for each function.

Another problem standing in the way is the CPU through which all requests for operations must pass (except some instances of interrupt handling). Centralizing command causes bottlenecks too and has been shown to be ultimately ineffective. Examples of the inadvisability of central command, in addition to computers are the Vietnam War, the USSR, and Cuba.

In order to escape shared resource architecture and central command in control systems, software must go. Aside from the mentioned problems, software also enforces linear-sequential operation, which is yet another bottleneck to responsive operations.

Software can thus be seen as a detriment and could be mostly unnecessary in the embedded control systems that encompass 98% of the billions of microprocessors (and derivatives) in existence. The only problem is how to write the software-less control-ware for those systems. I have the answer to that.