Interesting take. I don't really agree, php routes are handled natively and very simply and easy to reason about using the .php extension. Its the frameworker

Interesting take. I don't really agree, php routes are handled natively and very simply and easy to reason about using the .php extension. Its the frameworkers that broke that design with clean urls and fancy complicated routers. Php behind Apache or nginx is incredibly simple and easy to reason about. Browser loooks up this file url, this file url runs as a script and its output is returned. A bug in one file isn't propogated to all others so you can have highly reliable services with only partial failures from time to time. Whereas a bug in one route of a golang server may take the entire service offline. I do much prefer the deployment and shipability of a golang service, so much I am willing to give up the simplicity of PHP.