On the server-side PHP is used by 76.8% of all websites (a large chunk of that being WordPress). It is not going anywhere, soon. Looking at this statistics, nothing else seems to be even in the same league from a pure usage point of view.

I have yet to see a reason why it should change. Serious question: What is the disadvantage of using the tried and tested PHP8 compared to the alternatives, if you already know PHP?

[–] simonced@lemmy.one 9 points 2 years ago (1 children)

Serious Answer: PHP in itself is not that bad, despite some discussable decisions in function naming and arguments order to name a few. The biggest problem, is that it has a settings file describing how it works (php.ini) and that sh*t will bite you in the rear when you move apps from server to server, where all the libs are different etc... PHP never works out of the box when moving something on a new server, that is the worst part of the language.

[–] TCB13@lemmy.world 1 points 2 years ago (1 children)

Maybe the issue in your example isn't related to "how bad PHP is" but is to "how bad the code you're referring to is". Never had those kind of issues and yes obviously you've to know what extensions an application is using, but once again, modern PHP applications usually use composer as dependency manager and will gave those specified inside the project.

[–] simonced@lemmy.one 1 points 2 years ago (1 children)

Good on you to not have to maintain legacy code (15years+). Also, as a comparison, with JAVA, I have a legacy JAVA 1.5 to maintain, as far as you have the runtime, that stuff works, and that's it. This is how it should be.

[–] TCB13@lemmy.world 2 points 2 years ago

I do, the difference is that, unlike Ruby code bases, it happens to be supported languages that evolved and perform better today.

load more comments (6 replies)