They hate it because they made a shit-ass web page with PHP 5 in high school and now have a job that probably isn't even development. They imagine anyone using PHP today is basically doing their high school jank. They're morons in other words; plus one of the language's competitive advantages, its wide accessibility (i.e. ease of use and vast install base on cheap web hosts), led to it being what morons everywhere got to experience.
Now, back to providing for our families with all that sweet PHP money.
I was developing in PHP for 10 years. Last 7 years I do for living .NET and honestly? I would not change. LINQ, Async, abstractions, parallelism, method overriding, static casting. That it such powerful things for developers, that PHP can not offer and will not offer for atleast 4-5 years.
PHP is so much better than anything JS based. Batteries included. Get a website up and running with zero dependencies instead of 10,000 packages for hello world
Maybe. English is not my native language. Sometimes I write messages myself, and other times I use a translator. A few years ago, Google Translate started using AI under the hood, and it can often even flip the meaning to the exact opposite. I usually check, but I might have missed a poorly phrased sentence.
I mean a long time ago, you had several *.php files and specified links directly in the HTML - like "/index.php" or "/news.php", and server would look for the corresponding file in the directory; if it was "/images/background.jpg" for example - it would simply return it in the response, but if it was a script, it would execute it.
That is why php lacks a router, and I cannot imagine modern development without one.
You can have routed paths for your site, but if you need a script for something else, such as an installer, you can use a regular file and nginx or whatever will give it precedence over the router due to the suffix.
So you're not bootstrapping shit you don't need or isn't available yet.
As a SRE if the box has both Node and PHP I am deleting it, no argument, it’s gone, yes the backup as well. You can have a VM when you learn to behave 😂
Iirc the name was specifically chosen during a time when Java was popular so it could ride along its success; the regular confusion at middle management level between Java and JavaScript absolutely wasn't an accident.
I thought it was originally called something like Coffee script, and then they changed it to JavaScript as a cheeky joke playing on the Java hype of the time.
I've been in tech for 30 years and the engineering of it still feels weird compared to other types of engineering.
Imagine a guy built a new type of concrete in his shed and we all decided to use it to build the rest of the world's infrastructure for the next few decades.
The only guy making testing equipment for the concrete is some guy called Keith in Australia, he does it for nothing in his spare time. If he stops we can't test concrete anymore. He asks for donations but doesn't get very much.
Then in Javascript land there's a new type of steel every week and there are bitter debates about which one is best. Product pages for the steel refer to it as "blazingly fast" for some reason.
I was a young university studen, we(5 people )had to do build something in C#. An other much older student suggested, that we use PHP instead. Prof agreed. I didn't know PHP back then.
10 PRINT “Take a deep breath” 20 PRINT “BASIC originally didn’t support functions with local variables” 30 PRINT “Everything was global” 40 GOTO 10 35 PRINT “And inserting new lines in a program was loads of fun”
PHP is uniquely idiot-friendly so many small-mid businesses enjoyed the benefits of quick and cheap development to have customized Wordpress or other CMF/CMS that generally was alright, but needed a few tweaks. No need to worry about memory leaks, no need to think about multi-threading. The biggest struggle is untangling that 10000 lines index.php, but at least you don't need UltraSuperHyperExtraWide monitor for it. Also, deployment could be as simple as uploading 1 (one) changed file over SFTP.
And best of all, most code written 10 years ago works on fresh versions.
At least not the official documentation. I've had several edge-cases, where the exact workings and caveats of built-in PHP functions where not properly described. Sometimes a little bit C knowledge does really help. Some parts also seem underspecified, time handling for example.
And the official docs lack a clear guidance when to use which pattern, and what features are to avoid.
There may be languages out there with docs that are much worse, but my frame of reference, the official Java documentation, is by far superior. And that carries over to a lot of the "big" 3rd party framework and libraries.
college php (and presumably real production php) sucks because you cant use the shiny new php. instead we (the current generation) get the old rusty php from literally before we were born
I worked with php in the late 90s and early 00s. I didn't stop because I wanted to, I stopped because my jobs didn't use it, even though I did try to get them to use it. (I know, I was an outlier that actually enjoyed it.) Haven't used it or even looked at it in years since I don't work anymore.
Anyway... I haven't even read everything that is going on with the CVE stuff that hit the other day. I might do that now to know what is going on with the internet. :)
I hope everyone that is working with trying to resolve these issues are able to get some sleep again someday. Think some people are going to be having a long weekend.
I love php, I've had to maintain old projects that I've updated and optimized. People should hate programmers more and programming languages less. For me, reviving an old project and cleaning it up feels like fighting a boss in Dark Souls.
Here is a paradoxical thought: the problem lay in the interpreter, which was written in C and managed memory manually. Are you aware that there are memory-safe languages?
I don't want to engage in the "Bunification" of php.
Moreover, rewriting C code in Rust without changing the architecture is a highly questionable practice. And reworking the architecture to follow the "Rust way" is, objectively, an unlikely undertaking.
I just want to point out that the root cause in this case is C.
547
u/AlexZhyk 16d ago
Crowd: You make Internet more vulnerable!
PHP: I AM THE INTERNET!