The quote from Ken Stevens, whose opinion I respect, makes a compelling argument, and certainly Intel has a lot of expertise on asynchronous design, but I'm wondering if its position is similar to that of Kodak inventing digital imaging in the 1980s. That is, there would be less money for Intel to make in a future where asynchronous design prevails, so there's no incentive for them to develop it. With a properly exec…
This reminds me of 4GL hype.
I'd say it's the other way round. People have trouble learning synchronous logic design because everything happens in parallel, but it's a set of well-understood building blocks. Whereas asynchronous design is just entirely free of familiar reference points and there isn't quite the same set of standard idioms.
Yes, you get rid of setup/hold violations, but you're going to get a whole new class of problems with the addition that "timing closure" is now a moving target.
Async design in simulation is not some great hidden secret, it's just a trackless jungle. People are welcome to play with it; if you find a great way of teaching async design I'm sure we'd all like to hear about it.