I remember asking this same thing here.
I didn’t see so much added value in dedicating so many resources adding another server model to have everything abstracted behind Wappler’s framework.
It’s true it has neat features but that those neat features are not exclusive to nodejs.
Websockets is something that Wappler is missing at the moment that is true, but there are good php libraries that could be integrated by the team.
As I said php is not going anywhere anytime soon and I am sure it will adopt some of nodejs features through core or libraries.
Ok. Maybe not as natively and optimized. But for 99.99% of our use cases it will serve.
If we ever become the next world leading real time app I am pretty sure the team understands that we will have to graduate from Wappler and build something specific for our needs with our own team of 10000 engineers 
But until that time arrives maybe we shouldn’t use bazookas to kill mosquitoes and be wise about what we ask the team to build. It will probably take a huge amount of resources to build and maintain.
Instead of asking for nodejs why don’t we tell them what our specific use cases are? Then they can identify the actual needs and look for the proper tools to integrate with the current server models?