Hi > I am going to attempt to take that time on this draft in the next few days, > but please don't pretend that it's not a large undertaking for those who > haven't been living and breathing this RFC for the past year.
I don’t want to pretend that this RFC is simple. I want to express a different idea: by calling it “big” and “complex”, it’s easy to fall into the illusion that it’s impossible to analyze. Especially since the number of pages does not reflect complexity. Some parts matter more, some less. Some text is very important, while some is almost irrelevant. The amount of time needed to spend on this document depends on the goal. If the goal is deep analysis, it’s more like a week or two. If the goal is to grasp the core idea, it’s more like 15 minutes to an hour. The required time will depend on the reader’s background. If someone is familiar with coroutines in Python or JavaScript, or has worked with AMPHP or Swoole, this document should not be particularly difficult for them. I recommend looking at the PHP vs Python comparison documents right away: https://github.com/true-async/php-true-async-rfc/blob/main/comparison-php-python.md and for clarity, also at Go https://github.com/true-async/php-true-async-rfc/blob/main/comparison-php-go.md + Summary: https://github.com/true-async/php-true-async-rfc/blob/main/comparison-summary.md You don’t need to read all 55 pages here. If you understand this document, you can almost skip the RFC. It will be very difficult and painfully long only if someone is encountering coroutines for the first time in their life. But today, async has reached almost everywhere. Ed
