Systemd is mile ahead of the others, thing is that solves problems that you most likely don’t have or even know that exist. To boot a regular machine or small server pretty much any init system is good.
Not really incompatible, PHP provides configurable shared memory across processes that survive even if fastcgi releases every process and just keeps something idle for new requests.
don’t know a lot about fastcgi, but looking it up it seems like it also keeps a persistent process running to avoid execution overhead
More of less, the good thing about PHP + fastcgi is that it keeps a configure amount of minimum persistent processes (plus a dynamic number) to avoid execution overhead like you said... now there's an important detail, PHP processes are generic, meaning if you've 50 apps hosted in your server they can all be served with just one persistent process. No need to spin up 50 processes for each app like with node/go etc.
Supervisors shutting down containers/processes are good, but starting up is slow compared to the single PHP idle process ready to go for any app. :)
Exactly my situation. Thanks @mlunar@lemmy.world. The only way this could be done better was to do it in PHP / have fastcgi so it wouldn't require a constantly running background process specifically for it. People can say a lot of things about PHP, but nothing beats the fastcgi model.
It's not that is is a different ecosystem, it show shows how things can get bad very quickly. People like to say that they've the bridge that allows any generic IMAP/SMTP client to use their service, however what if they decide to disable the bridge? People talk a lot of shit about Microsoft and Google when it comes to email but at least those two provide email over standard protocols that can be used anywhere, not proprietary stuff. I wouldn't be comfortable with having my email hostage to proprietary stuff like that.
The spreadsheet is very opinionated for eg. Proton fails in integration very hard because you can't use it with a generic email client without extra steps... and in some platforms like iOS your only way to use it is by using their own app.
No, it isn’t. It should work if you do everything properly.
Systemd is mile ahead of the others, thing is that solves problems that you most likely don’t have or even know that exist. To boot a regular machine or small server pretty much any init system is good.
Basic Windows 95-era GUIs made with standard Windows APIs still look broken.
And the ones that survive that can be sterilized with vaccines, killed by cancer and/or bad nutrition caused by industrialized food products.
Not really, they seem to be doing the exact opposite.
Well, Telegram does the something for free.
Sure, but why? If you've a simple router running OpenWrt or something with all WAN ports closed you basically have the same thing.
People crying over Google copying Apple once again. What else? :D
The official website is https://bentopdf.com/ not what’s on the link.
The official website is https://bentopdf.com/ not what's on the link.
Why is it so hard to find a link to a github page? Is it even https://github.com/alam00000/bentopdf ? Also, the official website is https://bentopdf.com/ , not what the OP posted.
LOL. Do we more half baked features and bugs? No thank you.
@Xanza@lemm.ee latest code pushed into the repo splits the config into it's own file.
@Vendetta9076@sh.itjust.works latest code pushed into the repo splits the config into it's own file.
Not really incompatible, PHP provides configurable shared memory across processes that survive even if fastcgi releases every process and just keeps something idle for new requests.
More of less, the good thing about PHP + fastcgi is that it keeps a configure amount of minimum persistent processes (plus a dynamic number) to avoid execution overhead like you said... now there's an important detail, PHP processes are generic, meaning if you've 50 apps hosted in your server they can all be served with just one persistent process. No need to spin up 50 processes for each app like with node/go etc.
Supervisors shutting down containers/processes are good, but starting up is slow compared to the single PHP idle process ready to go for any app. :)
Exactly my situation. Thanks @mlunar@lemmy.world. The only way this could be done better was to do it in PHP / have fastcgi so it wouldn't require a constantly running background process specifically for it. People can say a lot of things about PHP, but nothing beats the fastcgi model.
It's not that is is a different ecosystem, it show shows how things can get bad very quickly. People like to say that they've the bridge that allows any generic IMAP/SMTP client to use their service, however what if they decide to disable the bridge? People talk a lot of shit about Microsoft and Google when it comes to email but at least those two provide email over standard protocols that can be used anywhere, not proprietary stuff. I wouldn't be comfortable with having my email hostage to proprietary stuff like that.
No. Same BS as Proton.
The spreadsheet is very opinionated for eg. Proton fails in integration very hard because you can't use it with a generic email client without extra steps... and in some platforms like iOS your only way to use it is by using their own app.