As Jaqui mentioned, the LAMP platform isn't just PHP. That P can also stand for Perl or Python.
The LAMP platform refers to use of Linux as an OS platform, Apache as the webserver, MySQL as a database back end, and Perl, PHP, or Python as an embedded scripting language. Perl and Python can both be used as embedded scripting languages with Apache modules for that purpose, though for maximum portability across different webhosts you're probably going to find that PHP is the only universally available option in that regard. You'd be hard-pressed to find a credible webhost that doesn't support PHP in all webhosting plans (static-page plans notwithstanding), but it wouldn't be difficult to find such hosting that only supports Perl through CGI and doesn't support Python at all.
Interestingly, Perl, PHP, and Python are all capable of running as either embedded or CGI scripting languages on an Apache webserver. If you have ultimate control over your webserver environment, I'd recommend going with Perl or Python over PHP, because both are much richer languages and don't suffer the same kind of security SNAFUs and bloat that PHP deals with. PHP can make for easier rapid development when doing things you're already used to doing, though, because whatever you're trying to do is probably accomplished by a function. Just keep in mind that rapid development doesn't always translate to quality development. You might have to write your own functions in Perl when the same task might be accomplished by a core function of PHP, but you'll also have more control over how the task is accomplished and, if necessary, it will be easier to translate to another scripting language.
If you're looking for alternatives to LAMP for much the same benefits, you should look into alternatives for each individual letter in the acronym, and consider the benefits and detriments of these alternatives.
L: Linux
Instead of Linux, you might look into FreeBSD or OpenBSD. FreeBSD is a very credible server OS. Its performance capabilities are about on a level with those of Linux, and it is nearly as cutting-edge. New versions of various server applications might lag a few months behind implementation on Linux, but for a stable server environment that may not be a concern. OpenBSD lags quite a bit, but is widely hailed as the most secure OS in the world. There has only ever been exactly one remote exploit vulnerability discovered for OpenBSD in default configuration, compared with the dozens for Linux and the hundreds for any version of Windows. You might also consider what flavor of Linux best suits your needs, which is a very involved discussion beyond the scope of this post.
A: Apache
There are other webservers available than Apache. Something that is increasingly being used in some instances is a combination of Apache and TUX servers. TUX is used to serve static pages, and Apache to serve dynamic pages. This, obviously, is only of use in instances where you're running a site that makes significant use of static (X)HTML pages, however. The major benefit here is in page loading speed for static pages, and in removing all static site load from the Apache server so that all its resources can be directed toward dealing with dynamic pages. For my purposes, it's generally a better idea to just run straight Apache sites and be done with it. There are other dynamic-site capable webservers out there, but generally Apache is the best combination of power, stability, speed, and flexibility that you're going to come across.
M: MySQL
In general, your best options for SQL database management systems are MySQL and PostreSQL. I have yet to come across any particular need for MySQL over PostreSQL, but it tends to be more widely used in large part because there's a greater user base. PostgreSQL is generally accepted to be the more scalable of the two, though you'll find some who claim MySQL is just as scalable (or at least should be as soon as better database clustering support has been incorporated in MySQL). There are bigger (and far more expensive) DBMSes available, such as Oracle, and smaller DBMSes like mSQL, but generally in any implementation where mSQL and its smaller siblings would handle the load, loads will be small enough on MySQL and PostreSQL implementations that you wouldn't notice any significant performance increase. In fact, if you're doing something small enough where MySQL starts to look too big, you should probably just be using flat files anyway.
P: Perl, PHP, Python
As already mentioned, each of these is an alternative to the others. There are other options as well. JSP is a big one, but generally suffers performance problems in comparison with LAMP under most circumstances since the server-side code must run on top of a virtual machine, and doesn't grant any particular benefits in exchange for that. JSP is basically the non-Microsoft answer to ASP. ASP can run on Apache, but that raises the question "Why?" Aside from simply migrating away from the vertically integrated Microsoft solution a piece at a time, I have a hard time coming up with any reason to do so. If you already have an entire site written in ASP, ASP on Apache might be a good direction to go, as an intermediary step toward migrating off ASP entirely, but it's not a final step by any means. You might want to look into other solutions, however, such as Ruby on Rails. Ruby is a "purely" object oriented interpreted language that is absolutely fantastic for web development on the server side, and Rails is a web development framework for Ruby. Look into it.
For use on a home-run website, PHP will probably suit your needs just fine. Ruby on Rails might be a good alternative for you, however, if you're willing to learn a language (though Ruby is an incredibly easy language to learn, as I'm discovering). Python is also easy to learn and quick in development, though I personally find it very difficult to look at. Perl is great, quite possibly the most flexible non-Lisp language out there. There's probably more Perl code already written for web applications than any other scripting language, as well, though you should be careful to check out the code to make sure it's not all BAD code (as you should with prewritten code from dubious sources in ANY language). Perl thus makes it easy not only to write your own code, but to avoid reinventing the wheel when code already exists for what you want to do.
I think that pretty much sums it up for now.