PHP, on the other hand, requires fifty packages and your sister's phone number before you get segmentation faults from the caching script and give up.
It's a bit telling that I essentially need to run a docker container for something so simple. Statically compiled binaries are super simple to use.
If accurate, then it's sad to see PHP to fall this way. I remember the good days when all it took to deploy your PHP project was (S)FTPing the code to a folder and pointing Apache to it.
At least the packages are often done professionally (e.g. symfony developed ones etc.). The standard library is pretty great so you don't always have to rely on packages. Often the same third party packages you'd have to rely on in PHP, you'd have to rely on similar packages for go.
> you get segmentation faults
Not sure where you get this from. In my 6 or so years of professional PHP development I've never seen a segmentation errors.
Anyway, still prefer a single go executable. It's just so much simpler.