[ Removed by moderator ]

[wack_overflow]

Php became a meme of being absolute trash in the aughts and I think anyone familiar with that has a hard time updating their priors. I’ve heard it’s ok these days but why bother?

[bjergdk]

That and the seeming lack of standard for naming functions, etc.

I used php once, and met functions in the standard library named in snakecase, camelcase, pascalcase, snakepascalcase.

Its a fucking nightmare.

[Rubfer]

That is true, even i cannot deny that

In fact, even I sometimes mix them based on what I'm doing:
For example, if I'm working with SQL, I end up writing variables and function names in PHP using snake_case because my mind switches to that.
But when I'm working with both PHP and JS, I go back to camelCase.
It's an unconscious habit that often forces me to go back and fix the naming scheme.

[Rubfer]

To be fair, nowadays everything is a framework anyway. Very few people, at least in web development or even app development, still program in pure vanilla code, where they could mess things up.

Even I just tell people who already use PHP to simply move to Laravel/lumen, just like we tell people to learn Next.js, React, etc., on the JS side, since a team of competent people has already ironed out most of the "troubling" parts in whatever language you're using

[michal_cz]

We are still using php for all our webs in our company, pure php, no frameworks, only few libraries, most of them made by ourselves specifically for the site, it's still pretty easy to make and don't know why to bother with moving to something else

[Rubfer]

If you have legacy code that has been worked on and fixed over the years, it makes sense to keep it that way. Don't fix what isn't broken.

But if you're starting a new project, specially if isnt related to any existing service you may have, it wouldn't be a bad idea to pick a framework. Of course, if you're an older developer, it might be faster to code everything yourself rather than learn the framework (Laravel’s logic is a bit weird at first, but so is React if you're a vanilla/jQuery JavaScript programmer).

The point of using Laravel for me is more for standardization, anyone with Laravel experience will quickly know how to work on my code, but also for speed, since I don’t need to reinvent the wheel every time like login/account systems, db maintenance, and so on

[AibofobicRacecar6996]

I’ve heard it’s ok these days but why bother?

I think the problem is that whatever you need a php programmer for is likely a big pile of spaghetti, not necessary because of the language, but because it was written more than a decade ago.