Imho, while i agree on the marketing side of the problem, there is one more, and probably, worst problem: at $JOB, every single PHP you're going to find has to be treated as legacy, no shiny stuff, no proper sane way to work with it, incosistent envs unless you're lucky enough to have a dockerfile and some scripting that can do the heavy lift for you.
All of this for the second lowest wage after JS devs. Not worth it.
I'm using Go and i'll never go back in the immediate future: go run . and i have all of it. Period.
WASM is not so supported, but it's not like a major technology right now.
If you need complex UIs, separate backend and frontend and write the latter in something well supported (like, i dunno... JS)
"The days of crappy NPM packages are over" said no one ever, and no one will ever say.
TS is never going to catch up with Go performances, and the lack of IPC and true concurrency actually is very bad for backend services that need to handle stuff.
I think the OP wants to use Go for stuff that isn't supposed to do with.
All of this for the second lowest wage after JS devs. Not worth it.
I'm using Go and i'll never go back in the immediate future: go run . and i have all of it. Period.
PHP should strive for something like this.