Re:Moving from Go to PHP Again
by chiefalchemist on Friday February 08, 2019 @12:09PM
(#19116310)
> "...especially WordPress deployments."
I've done enough WP to certainly agree with you. However, I don't think it's fair to judge PHP by how WP has abused it.
WP problem is its desire to sacrifice code quality and best practices for market share. That is, many things don't get refactored (into something OOP based) because there might be backwards compatibility issues. Again, this isn't PHP's fault.
I'm not all out against PHP. I've used, and still do, on occasion for simple things and prototyping.
That said, I'll never go out of my way to use it for much else—let alone serving and routing something public-facing ever again.
Re:Moving from Go to PHP Again
by KerryJones on Friday February 08, 2019 @12:33PM
(#19116585)
Checkout Laravel, it powers some Fortune 100 sites -- it's definitely "large-site" capable.
Re:Moving from Go to PHP Again
by chiefalchemist on Friday February 08, 2019 @01:56PM
(#19117490)
I did one project in Laravel. I was impressed. That said, it takes WP to the opposite extreme. That is, it is has little regard for backwards comparability. Finding answers / examples via The Google is messy and frustrating, at least for someone who was new to Laravel.
I like that it's forward-thinking, but it moves so fast that it has negative impact on user (i.e., dev) experience.
Re:Moving from Go to PHP Again
by lwansbrough on Friday February 08, 2019 @01:31PM
(#19117205)
Laravel performance is abysmal, though. You're gonna spend 10x on server costs if you use a fully featured framework in PHP.
In a complex product (as in, most professional settings or large services/web sites) the PHP I've seen is grossly complex, and not intuitive—especially WordPress deployments.
Dev teams have to perform all kinds of gymnastics with the PHP code to get it to do what they want, and it's just a flat out nightmare that I've made sure my boss and colleagues know that I have no desire to work with it.
It always ends up a house of cards and full of vulnerabilities so that something is regularly getting exposed that allows at least editorial access. Security issues that should otherwise be no problem.
God knows how many other vulnerabilities exist. Every single server I've ever had has had bots and crawlers polling for common PHP files in an effort to exploit them, should they exist.
I just don't like having even the chance that my back-end source could, for want of a single character, spill out to a web page upon request.
And then there's performance...
Anyway for simple things, sure. For things that don't require much security, sure. For anything else... it's not for me.