This is bad advice. Mocking libraries have come from many years of experience. Rolling your own test library will be like reinventing the wheel, but with less documentation and more inconsistencies.
@symfonystation I’ve been using systemctl restart php-from for a long time.
The problem with any of these other tools is that they always rely on some php code to refresh the opcache. But what if the opcache has an outdated version of that code cached?
I’ve been bitten by it a couple of times. So restart php-fpm is far more reliable for me.
Just using PHP is making me want to stop using it. There are so much code out there that they keep deprecating consistently for a while now.
I know they are trying to make it better, but we are already used to it being shit. We worked around those issues. Now we have to work again to adapt to new rules.
If you, like me, are creating a website. I would advise you to pay attention to the website database. This is a very important indicator and the key to success. Databases are very important now and turn a website into a dynamic platform.
@symfonystation This seems like a shocking indictment of Ubuntu 20.04 to me. Is there any analysis of the underlying reason? I couldn't find any in this article.
@symfonystation I don't get it, are loops now evil? Why would one want to not use them? Stuffing arrays into collections in order to manipulate them "nicely" is not a crime, sure. I just have a problem understanding why the other way is presented as bad/no-no.
@symfonystation The real issue here is that too many PHP applications are not configured to work with a single PHP entrypoint, instead, they enable any dot php file to be served. This is criminal often, specially on nginx where you can't ship these rules like Apache (an .htaccess file on web root) and users share their own rules without realizing the hazardous conditions.
PHP
Hot