Re: Re: [RFC] True Async RFC 1.7

> I don't like this experimental model or introducing API stability levels as it is > confusing for users. It requires extra checking for users to do for each API (no one usually does it > and with AI it will be even more problematic because it might not tell that the generated code uses > experimental API). This would just become pain for user and I don't think it would be good for > PHP. I think this is a good topic for discussion, and we could talk about the pros and cons of a “nightly” build. I could explain how early product delivery improves code quality. > That can be already done but it will never guarantee that the second vote will succeed. It's OK! But at least I would know that the PHP community truly wants to make the language asynchronous. I still don’t understand the answer to that question. It seems to me: no. We could probably include a vote in this RFC on three core principles: * concurrency * transparent asynchronicity * cancellation to see how many people support them. If more than one third vote against it, then we can safely stop trying to change anything.