168 karma · joined October 31, 2023
I can understand the work network policy, someone could use Tailscale to leak data, but a residential ISP should not block it. I would rather bother their support for an incomplete service.
Additional measures are certainly required.
But it’s not the language itself, as I was advised. True asynchronous handlers are possible, which is promising.
> Person writing this is not very experienced, because this hasn't been the norm for a long time.
I’m genuinely curious—what is the norm here now? I see a lot of PHP code, and 90% of it is just setting up the environment from the ground up, while only 10% is the real processing. The good side is being stateless, but the performance penalty is enormous. I still see a lot of file caching (please make this dir 777 for production) to mitigate some of it, but Redis has become remarkably visible over the last years.
Not being a PHP expert, I really need some best practices to point devs to.
I do understand the counterpart party problem, it is not someone can control. Sent once, it's free to be seen by anyone.
P.S. I’m not a lawyer, obviously.