Hello, Daniil. > Essentially, the only thing that’s needed for backwards-compatibility in most cases is an API that can be used to register onWritable, > onReadable callbacks for streams and a way to register delayed (delay) tasks, to completely remove the need to invoke stream_select.
Thank you for this point. It seems I was mistaken in thinking that there is a Scheduler inside Revolt. Of course, if we're only talking about the EventLoop, maintaining compatibility won't be an issue at all. > I’d recommend chatting with Aaron to further discuss backwards compatibility and the overall RFC: I’ve already pinged him, he’ll chime in once he has more time to read the RFC. That would be really cool. > To Edmond, as someone who submitted RFCs before: stand your ground, try not to listen too much to what people propose in this list, > especially if it’s regarding radical changes like Larry's; avoid bloating the RFC with proposals that you do not really agree with. Actually, I agree in many ways. In programming, there's an eternal struggle between abstraction and implementation, between strict rules and flexibility, between paternalism where the language makes decisions for you and freedom. Each of these traits is beneficial in certain scenarios. The most important thing is to understand whether it will be beneficial for PHP scenarios. This is the main goal of this RFC stage. That's why I would really like to hear the voices of those who create PHP's code infrastructure. I mean, Symfony, Laravel, etc. Thanks! Ed.
