> When you already have a solid background in PHP, it will be much easier for you just to dig in some libraries and tools for your use-case, instead of learning a new language and a new ecosystem.
The main challenge when going async isn’t learning new syntax. It’s dealing with non-linear flow control and with different abstractions.
So, I remain unconvinced that picking PHP’s comparatively obscure async ecosystem is a good longterm strategy.
This sounds very plausible to me. As well as PHP, I've written a bunch of Java and threaded Java. I treat the latter two as different languages: yes you can use the same parser for both, but adding threads to the semantics also removes a lot of the mental models and assumptions we could previously make.
The main challenge when going async isn’t learning new syntax. It’s dealing with non-linear flow control and with different abstractions.
So, I remain unconvinced that picking PHP’s comparatively obscure async ecosystem is a good longterm strategy.