Well, that last bit is not true. You can use PHP for more than just Web.
As for the other part, well, you can call them noobies if it makes you feel better, but for someone who has been doing this for more than 20 years, all developers who complain about one framework or the other look like noobs. All frameworks have their pros and cons, and the best point made in your post is that the cons almost always come from people who don't know what they are doing, but that point hurts you when you start complaining about Node because well... do the math.
Again, I'm not complaining about Node. I'm complaining about the people who constantly keep pushing Node to others.
The difference lies in the fact that I'm not trying to force my opinion on anyone about JavaScript. People who keep pushing JS everywhere do.
I believe JS does fine for client side, that's what it was meant for. But the community started trying to bring it to everything else too. And the newcomers somehow fall into the trap of blindly following any cool new framework that comes their way and they keep pushing it everywhere.
I'm sure more experienced developers like yourself understand that languages are just tools and some tools are more fit for some things better than other.
And yes, you can use PHP for other things too. But you wouldn't do it in production in your right state of mind.
Node works fine in other areas, too. It's got plenty of things I dislike and wouldn't be my first go-to in most cases, but implying that it doesn't belong in those areas is the same backwards thinking as "PHP is trash".
My point is, you have kind of a roundabout way of putting down the other guy in the same way that you've probably been put down, and most likely, neither really deserve it.
As for that production comment, I'm going to disagree with you again. Consider if you have a framework that includes a PHP library that is the center for managing certain entity types. That functionality may include file i/o, database ops, external API integrations, etc., now consider your CI needs to perform some manipulations in certain workflows, would it be smarter to rewrite that functionality in another language or use PHP and import the library you already have?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well, that last bit is not true. You can use PHP for more than just Web.
As for the other part, well, you can call them noobies if it makes you feel better, but for someone who has been doing this for more than 20 years, all developers who complain about one framework or the other look like noobs. All frameworks have their pros and cons, and the best point made in your post is that the cons almost always come from people who don't know what they are doing, but that point hurts you when you start complaining about Node because well... do the math.
Again, I'm not complaining about Node. I'm complaining about the people who constantly keep pushing Node to others.
The difference lies in the fact that I'm not trying to force my opinion on anyone about JavaScript. People who keep pushing JS everywhere do.
I believe JS does fine for client side, that's what it was meant for. But the community started trying to bring it to everything else too. And the newcomers somehow fall into the trap of blindly following any cool new framework that comes their way and they keep pushing it everywhere.
I'm sure more experienced developers like yourself understand that languages are just tools and some tools are more fit for some things better than other.
And yes, you can use PHP for other things too. But you wouldn't do it in production in your right state of mind.
Node works fine in other areas, too. It's got plenty of things I dislike and wouldn't be my first go-to in most cases, but implying that it doesn't belong in those areas is the same backwards thinking as "PHP is trash".
My point is, you have kind of a roundabout way of putting down the other guy in the same way that you've probably been put down, and most likely, neither really deserve it.
As for that production comment, I'm going to disagree with you again. Consider if you have a framework that includes a PHP library that is the center for managing certain entity types. That functionality may include file i/o, database ops, external API integrations, etc., now consider your CI needs to perform some manipulations in certain workflows, would it be smarter to rewrite that functionality in another language or use PHP and import the library you already have?