I think the way to analyze a language and framework should be: "what does this framework permit the worst developer on the team to do?"
I think the story for Php in this regard has not been a good one historically.
You can put processes like PR review, and add coding standards, but getting things done will always trump those things, especially when you are bootstrapping.
If you can tell me modern PHP is better than the alternatives at preventing bad behavior (or encouraging good behavior) then I'm interested. But, this post didn't move me to change my mind there.
A language that has to permit this kind of thing (or thinks it has to) is just going to lead to developer infighting. This is an important issue because GitHub PRs are going to be unreadable if one developer can insist that "this line needs to be 145 characters..." and then no-one can diff changes to that code. You can break the PR process with this kind of thing.
I'm not sure what this has to do with PHP as a language... barring the few languages with a very strong default formatting convention like Go, code style differences are both a fact of life and not terribly problematic (set rules for the project and enforce them automatically).
I think the story for Php in this regard has not been a good one historically.
You can put processes like PR review, and add coding standards, but getting things done will always trump those things, especially when you are bootstrapping.
If you can tell me modern PHP is better than the alternatives at preventing bad behavior (or encouraging good behavior) then I'm interested. But, this post didn't move me to change my mind there.