This is incredibly useful when learning basic web development, even though it doesn't scale for more complicated applications.
It's also incredibly useful when trying to bang out a simple experiment.
These features of PHP are still eminently useful if you have to do the dirty one off. You can eliminate a massive amount of time pressure (an emergency or time invested vs time saved) if you dont have a ton of overhead that comes with modern frameworks.
Unfortunately it also provided a lot of careers to developers who never got to the "make it" stage.
Because many times, they write bad, buggy software. Because other people end up having to maintain it, or fix it, or replace it. Or they release things like plugins that malfunction, but because they're the best out of a set of bad options, end up being the de-facto solution that everyone has to deal with.
I'm not talking about people who build software that works ok, but has bad patterns. I'm talking about people who write cash register software that uses floating-point math to do calculations, or Wordpress plugins that fill up error logs with garbage or nearly DDoS sites because they don't understand how to write efficient code.
Not that I've done any of the above as an early PHP developer, no sir...
PHP made a lot of careers for developers as they were able to fake it until they made it while learning how to code & providing significant value to a businesses.
While PHP is nothing like its former self, most people who developed web apps in the first decade of the century will probably always remember PHP for what it was.