PHP was my first web language and I built my first web application in it in school.
I don't use it anymore really and honestly haven't used it in a few years. One of our clients has an application that is built on like PHP 5.1.x. It's very old. What makes it worse is that the application is built on top of some really old CMS platform that is no longer a thing and has zero documentation on the internet anymore it seems, or that we can find. We have tried to upgrade the version of PHP it uses but immediately ran into issues where everything would just break. So we still haven't gone down that rabbit hole yet. The code base is also a very delicate thing. You have to be careful changing anything cause it could break so much. Though the application is just so large that paying for a rewrite isn't doable right now.
I myself have no problem with a more modern PHP codebase. Language is simple. It does its job and does it well. It's just not my cup of tea really. I myself just don't like to get old PHP projects from clients because most of the time it just seems they are beyond saving. But that very well could be me since I don't use PHP everyday anymore, and don't know the upgrade process for a really large, poorly documented, PHP project.
I see a lot of projects around like this one. Tons of security vulnerabilities, so much bad code because of this "fast shipping" mentality. What I think is; it is because of the developer not because of the language.
There is no doubt it is the developer and not the language. You can write bad code in any language.
I didn't mean for it to sound like I'm blaming PHP. There is no doubt it is just how it was built and not the language. You can write bad code in any language and any framework.
I do think that maybe older languages see it more since you will have to deal with older code bases a lot more.
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.
PHP was my first web language and I built my first web application in it in school.
I don't use it anymore really and honestly haven't used it in a few years. One of our clients has an application that is built on like PHP 5.1.x. It's very old. What makes it worse is that the application is built on top of some really old CMS platform that is no longer a thing and has zero documentation on the internet anymore it seems, or that we can find. We have tried to upgrade the version of PHP it uses but immediately ran into issues where everything would just break. So we still haven't gone down that rabbit hole yet. The code base is also a very delicate thing. You have to be careful changing anything cause it could break so much. Though the application is just so large that paying for a rewrite isn't doable right now.
I myself have no problem with a more modern PHP codebase. Language is simple. It does its job and does it well. It's just not my cup of tea really. I myself just don't like to get old PHP projects from clients because most of the time it just seems they are beyond saving. But that very well could be me since I don't use PHP everyday anymore, and don't know the upgrade process for a really large, poorly documented, PHP project.
I see a lot of projects around like this one. Tons of security vulnerabilities, so much bad code because of this "fast shipping" mentality. What I think is; it is because of the developer not because of the language.
There is no doubt it is the developer and not the language. You can write bad code in any language.
I didn't mean for it to sound like I'm blaming PHP. There is no doubt it is just how it was built and not the language. You can write bad code in any language and any framework.
I do think that maybe older languages see it more since you will have to deal with older code bases a lot more.