There is a huge difference between "PHP is hot garbage" and "I think PHP is hot garbage".
Indeed. And I would agree with both statements. There's plenty of things that make me personally dislike PHP as a language, but there's also a good list of reasons why I think PHP is objectively a bad language. Things like the inconsistency of built-in function names only make it harder to use without adding anything, while features like OOP add something that others enjoy but I don't personally care about.
pointing out that it is used by many to good use.
Just like how transformer oil is used by many to deep-fry food. That doesn't automatically mean it's a good or a bad thing, it just means that lots of people do it. A more important question is: Could these same people be achieving even more if they were to use another tool instead?
Heck, it even kept me from using Rust for years because I got piled on, called irresponsible and outright criminal because I was working in C++.
Unsurprisingly. As someone who hasn't tried Rust, the two cliches I predominantly associate with the language are transgender cat girls nyaaa~ and elitism (from my experience, these two seem mostly disjoint though).
As far as community involvement goes, most of my experience is with the Lua community, which is rather small, so that may be an important factor. Most of the interactions I've seen are generally more leaning towards "PHP is shit, here's why, here's some alternatives and if disagree I'm curious to hear your opinion" (replace PHP with any other hated technology).
In other words, people have the same strong opinions as anywhere else, but with a healthier attitude towards different perspectives.
PHP 8 is a joy to use and the ecosystem is insane: there are few web frameworks as good as Symfony out there... Django or Rails don't match Symfony.
Some php devs prefer laravel but I personally don't like when there's too much magic.
My point is that in the industry, very few teams use php without Symfony or Laravel's tools. They also mostly use things like static code analysis tools to catch edgy errors.
Some will argue that if those tools are needed then the language is bad... Maybe, but I don't know any language that would make me more productive than PHP and Symfony for doing SOLID server-side programming, not even nodejs.
Slack dev team wrote a great article about why they they came back to PHP for their server side stuff.
Indeed. And I would agree with both statements. There's plenty of things that make me personally dislike PHP as a language, but there's also a good list of reasons why I think PHP is objectively a bad language. Things like the inconsistency of built-in function names only make it harder to use without adding anything, while features like OOP add something that others enjoy but I don't personally care about.
Just like how transformer oil is used by many to deep-fry food. That doesn't automatically mean it's a good or a bad thing, it just means that lots of people do it. A more important question is: Could these same people be achieving even more if they were to use another tool instead?
Unsurprisingly. As someone who hasn't tried Rust, the two cliches I predominantly associate with the language are transgender cat girls nyaaa~ and elitism (from my experience, these two seem mostly disjoint though).
As far as community involvement goes, most of my experience is with the Lua community, which is rather small, so that may be an important factor. Most of the interactions I've seen are generally more leaning towards "PHP is shit, here's why, here's some alternatives and if disagree I'm curious to hear your opinion" (replace PHP with any other hated technology).
In other words, people have the same strong opinions as anywhere else, but with a healthier attitude towards different perspectives.
PHP is good at what it does: web oriented OOP.
PHP 8 is a joy to use and the ecosystem is insane: there are few web frameworks as good as Symfony out there... Django or Rails don't match Symfony.
Some php devs prefer laravel but I personally don't like when there's too much magic.
My point is that in the industry, very few teams use php without Symfony or Laravel's tools. They also mostly use things like static code analysis tools to catch edgy errors.
Some will argue that if those tools are needed then the language is bad... Maybe, but I don't know any language that would make me more productive than PHP and Symfony for doing SOLID server-side programming, not even nodejs.
Slack dev team wrote a great article about why they they came back to PHP for their server side stuff.
slack.engineering/taking-php-serio...