MDM wrote:
so one mathematical process triggers the next at the end of it's own computation
Which means that the result is generated as fast as the hardware can process, potentially much faster than a clock tuned to cope with maximum latency, but only runs when there is a need. The hardware does what it is designed for potentially very much faster than clocked designs, but with very much lower power consumption.
But the problem then is, how do you design a general purpose computation unit for which programmes can be written, or for which programmes can be compiled? There are successful systems in specific applications, like traffic management, that are very well suited to asynchronous design. Most other problems are not well-suited to asynchronous design, or our brains are not well-suited to structuring our problems in asynchronous terms. Mostly there has not been a successful asynchronous processor design or computing language that fulfills general purpose needs.