Hello. > I don’t think that’s universally true, or at least it hasn’t been my > experience. As far as I know, there is no universal truth. PHP plus asynchronicity plus a crisis of trust is a very specific situation. And it has existed longer than this RFC. It’s a fairly large topic for discussion, and probably uncomfortable.
> When I personally stepped back Lately, I’ve been hearing the phrase “take a step back” quite a few times. But believe me, not a single person who’s said this to me has been able to clearly explain what they actually mean. What does “a step back” even mean? > I want to be clear about something important, though: this isn’t a lack of > interest in asynchronous capabilities in PHP, nor a lack of willingness to > help. * Python got asynchronicity in 2015. * Python is a general-purpose language, and asynchronous I/O is not a critical feature for it. * PHP still hasn’t gained asynchronicity. It’s 2026. * For PHP, asynchronicity matters more than it does for Python. On top of that, there have been some attempts by different people to add asynchronicity to PHP, all of which either failed or were ignored. So there is interest in asynchronicity, but it seems to be buried very, very deep :) > contributors need to feel that concerns are being heard, trade-offs are being > explored together, and iteration is genuinely collaborative. * What concerns? * What collaboration? What is this actually about? Everyone who wanted to collaborate on this RFC has already done so. I’m running this project 100% openly, there isn’t even a private chat. Only a few ideas were discussed privately over email, and I always write about the outcomes of those discussions publicly. > If the process moves in that direction, breaking things down, explicitly > engaging with criticism, and evolving the design based on shared input, I > think you may find that more people are willing to invest time and energy > into it. Sorry, but I don’t understand anything from this sentence at all: * Which direction? What’s wrong with the current one? * Into what parts should things be broken down, and why? * What does “explicitly engaging with criticism” mean? And what kind of work was being done before. Implicit? Hidden? * What does “evolving the design based on shared input” mean? Who is stopping you from contributing to an open repository? Who is this person who is forbidding it? Tell us who they are and we’ll punish them :) And you seem to be missing the most important point: * this project is not something I personally need. * It’s not my project that people aren’t joining. * The TrueAsync project was created first and foremost for PHP itself. * PHP is the one that needs it. I am already an experienced and fully capable developer without it. I don’t need to prove anything to anyone. The problems with the process of accepting large changes to the language cannot be solved by me. They are outside the scope of my responsibility. I don’t need to solve it. I don’t need to create working groups. I don’t need to write private emails and ask everyone to vote. I’ve already done the work within the scope of the responsibility. The remaining percentage of success no longer depends on my actions. --- Ed
