9 ms·

I developed in PHP professionally for a while. The language was objectively terrible. But Laravel was great, and so was TLOEP, and some other stuff. I think the

I developed in PHP professionally for a while. The language was objectively terrible. But Laravel was great, and so was TLOEP, and some other stuff. I think the reason people would ridicule it so much was due to how many bad libraries, bad practices, and bad information was prevalent within the community. The community may have been welcoming, but much of the time it was the blind leading the blind. My understanding is that it has improved dramatically over the past 10 years.

ramon156 2y ago
I relate to this, but replace Laravel with Symfony. I think the majority of people just echo whatever the internet says. Reddit is really good at this, and it's a bummer that the internet enforces this.
sam_lowry_ 2y ago
In 2001 and even in 2011 PHP was a thin poorly thought wrapper around C stdlib and many other popular libraries. One thing it got right is shared-nothing architecture where a PHP instance effectively spawns for each request and then dies. I heard it was called "PHP must die architecture", probably as a tongue-in-cheek reference to haters or to a 2000 film with Jet Li. By 2009 I switched from EJB-ridden Weblogic-posessed Java programming into PHP prigramming, and it was a breath of fresh air. Unfortunately, it paid much less. Nowadays PHP is in pretty much the same situation as JavaScript: rotten to the core, but great nevertheless if used properly.