I can argue that the AMP (particularly XAMPP/LAMPP: apachefriends.org) could be *better* in a production environment, at least in some cases. For what it's worth, I'm pretty particular about my systems, and I'm running them on XAMPP. Clean, duplicatable, easy, powerful. Don't overlook duplicatable: systems that are easy to replicated are usually much more stable...per my experience.
I occasionally have to build stuff from scratch, namely modules for apache add-in. I end up building from apache source, even making my own apache executable set. But I run from XAMPP/LAMPP, nonetheless.
On linux/redhat9, I try to funnel all my system customizations in /opt. LAMPP installs by default in /opt/lampp. I usually build everything else in /opt/local. Therefore, when I want to duplicate my system, I tar up /opt, then untar it on my new system. DISCLAIMER: I have yet to test this yet with *all* of my /opt, but I have done it with /opt/lampp (which is really just reinstalling LAMPP), and I find it works well.
Furthermore, the LAMPP upgrade process is all nicely bundled. It appears to work well. I have yet to experience it much, although I have progress from XAMPP 1.4.5 (on windows) to LAMPP 1.4.9a with the same/similar server
apps and data. No problems that I recall.
Oh yeah...this little fact that I migrated across heterogenous operations systems is a BIG deal in my book.
I suspect someday I might get heavy with apache or mysql
customization and might want to diverge. Until then, I love my XAMPP/LAMPP.