PHP 8 for our API, JS for the app that consumes it - sharing code both server-side and client-side.
It works really well for us.
Development on a modern version of PHP with a framework like Symfony or Laravel is so very different to development on old PHP5 versions.
edit: PHP 7.x and 8 let you do things like:
- no automatic type conversions
- typed function parameters and return types
- typed object properties
- named parameters
All of these are little niceties but they add up to making it fantastically easier to avoid stupid mistakes that used to be common with PHP.
Kids who want to seem cool have moved on to Go and NodeJS, so PHP is mainly left with people who got some experience and mostly know what they are doing, save for those who really just twiddle Wordpress until it sort of appears to do what they want it to do.
I suspect that PHP's ultimate fate is to become another Perl — a quite mature platform with very few people tending to it, obscure, with a community of very expensive veteran programmers.
https://www.php.net/supported-versions.php https://www.php.net/releases/8.0/en.php
The thing with PHP is it's very easy to understand in comparison with Perl. When Facebook did a study on which languages take the least amount of time to onboard new hires PHP won every time. It's also why they use their own version of PHP in house (Hack). It's 95% same thing with additional features like async built into their engine.
The language itself at the time was mostly useful because you could execute a script made of HTML (or anything really) with some embedded magic tags interpreted as PHP instead of the opposite where you had to do some sort of template engine.
I don't disagree that it was useful — especially for having such a simple “upload a file, hit refresh” workflow — but popularity can work against you when it encourages optimizing for easy starts over long-term maintainability and a huge number of people learned dubious habits and aren't quick to switch.
1: https://insights.stackoverflow.com/survey/2021#technology
Only developers complain about PHP. And even that isn't really warranted anymore as PHP has grown leaps & bounds since most of the hate.
I just inherited a PHP project that it's a nightmare. It doesn't make any sense. It works on PHP 7.3 but the quality is worse than the old PHP 4 stuff.
It is so easy to write good PHP code nowadays but most devs don't do it. They just go for the old ways, with spaghetti code, no clear architecture, etc, because it just works. They don't have to think, just type. Thats why people hate the language. They see the bad code and they think the language is poorly designed.
I highly encourage using this template for all new projects
The project not only doesn't use composer (well, it does now because I needed some components) but it has the same third party components duplicated or triplicated around the application. It looks like they downloaded them Everytime they needed them. Some of them are modified to make them work on newer versions of PHP. And the views and the logic are mixed together in big 4k lines files with no functions. Html, js, PHP, tens of SQL queries on loops, all mixed together.
It's so bad it looks that it was made like this on purpose.
The funny thing is a pretty important project for a pretty important and unique customer.
Just want to nuke everything to oblivion.
But there is hope, sometimes it can be better to inherit badly written repetitive & copy-pasted code, rather than badly written abstractions.
Badly written abstractions can be really hard to get out of years later because it tends to be viral all over the project, however when there are no abstractions at all, you can decide them right now, you are in charge. Bit by bit you can unwind this mess to something grander, to your own creation. Good luck. Praying the PHP prayer for you.
For the last couple weeks I've been thinking I should look for a new jobs as it looks there's no future here.
You start by setting up the standard router for all URLs when the php file doesn't exist. You then setup your router to answer somefile.php or whatever file you want. You then have that route execute your own class. You simply delete the original file and it now loads from your router. You can typically copy/paste the code from the file into a function in a class without any modifications. As you go you can get rid of includes / requires all over the place because now you've got auto loader configured so you can just call code from other files at will.
So then I just repeat this process. Sometimes it takes years but I can typically make a huge dent in most systems in the first few months.
If I don't get buy in I do it anyway for any code I'm asked to work on cause it makes the work better and there's no reason not to do it at that point.
I actually kind of envy you. I enjoy refactoring projects like that. You can typically bring that 4k line file you mentioned down to just a few classes and views.
But... is it much easier to find good devs in any other tech stack? I don't see it, personally. My ruby friends complain it's hard to find ruby devs at all, and harder to find good ones. I do see a lot of JS/node folks that get accepted as 'good', but when the rubber hits the road, the code is often still... meh - cut corners, SO copy/paste, etc.
I see bad node and bad js and bad python... but somehow the languages and stacks get a pass and "it was just a bad developer". But if you see bad PHP, people think "the whole language sucks". Completely inconsistent.
Compare that with deploying a hello word website in python, java or elixir.
Note that I enjoy both PHP and JavaScript immensely. But, my God, some of the code that I've seen in both languages...
OTOH many bootstrapped or legacy companies pick long established technology to build their products as they are only selling product implementation, not the idea of changing the world or whatnot.
It might also be the client simply wants php. They don't want to pay to maintain anything extremely over-engineered.