3 ms·
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 archi
by 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.