>
> Neither of these is a bad use case, and they're not mutually exclusive,
but they do lead to different priorities.
> I freely admit my bias is towards Type 1, while it sounds like Edmond is
coming from a Type 2 perspective.
>
Exactly. A coroutine-based server is what I work with, so this aspect has a
greater influence on the RFC. However, both cases need to be considered.
Right now, background services are handled with Go. If PHP gets solid
concurrency tools, convenient process management, and execution tracking,
the situation might shift in a different direction—because a unified
codebase is almost always more beneficial.