[throwaway92748]

I used PHP several years ago and are considering trying it again for my side hustles. You basically just push files to a folder and "forget about it"

It just keeps running and auto corrects any temporary load issues because of its stateless nature. I don't have to worry about memory leakage or processes that eventually become unresponsive and needs to be restarted. If the unlikely event that the PHP process crashes, it will just restart automatically and handle the next request as if nothing happened.

Its the ideal solution for side projects, and I am definitely going back now that I don't have time to maintain complicated infrastructure.

PHP was my generation's version of AWS stateless "lamda". Just place a file in the folder, and it will be executed on demand and clean up resources after the request has ended. A server could handle many different websites at the same time. That was basically how we could get cheap webhosting. They just put a bunch of Apache-instances behind a load balancer and used a shared network drive to read the files from

[kunley]

The "push files and forget" mindset is why PHP is a nightmare for operations on a serious production.

To be fair, it shows up as a nightmare from a certain scale. Toy projects might not reach this level..

[1oooqooq]

if you reach a certain scale and still do that, the language is the least of your worries.