From 28bebac6496fe95890e6fd6745b971d381c63d29 Mon Sep 17 00:00:00 2001 From: Court Ewing Date: Wed, 28 Dec 2011 15:54:36 -0500 Subject: [PATCH] Updated internal link --- ...011-08-31-how-php-is-broken-and-how-it-can-be-fixed.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2011-08-31-how-php-is-broken-and-how-it-can-be-fixed.markdown b/_posts/2011-08-31-how-php-is-broken-and-how-it-can-be-fixed.markdown index 8e812db..f56dfdc 100644 --- a/_posts/2011-08-31-how-php-is-broken-and-how-it-can-be-fixed.markdown +++ b/_posts/2011-08-31-how-php-is-broken-and-how-it-can-be-fixed.markdown @@ -12,7 +12,7 @@ How PHP is Broken and How It Can Be Fixed **Edit (Nov 14 2011 6:03pm)** The follow-up article is posted [here][followup]. -[followup]: /2011/11/follow-up-how-php-is-broken-and-how-it-can-be-fixed.html +[followup]: http://epixa.com/2011/11/follow-up-how-php-is-broken-and-how-it-can-be-fixed.html **Edit (Aug 31 2011 8:05pm):** When I started writing this article, my intentions were to criticize the PHP core developers for what I consider to be a severely broken process. I do want to make that clear. As a member of the community and a long-time PHP programmer, I find it indescribably irritating that a failure as significant as the release of PHP 5.3.7 could happen without the dev team at least backing up the release of PHP 5.3.8 with an analysis of exactly what happened and exactly what measures were being considered so that it never happened again. The problem here is not that a human made an error, the problem is that there were no measures in place to stop that error from happening, and so far there hasn't been (or I haven't seen) an official explanation of what measures will be put in place.