See, for example, my comment in this thread: http://news.ycombinator.com/item?id=595513
PS: Which is something to think about, if you are spending as much money on HW as Google it might be a good idea to use C or other fast but hard to write language for some of your core functions.
I think this argument in some ways hinges on how far from the tree you're falling. If you're doing essentially a variation on a common theme, you'll be the fastest by picking a language where the bulk of the work is already done for you in a variety of reusable modules. It'd have to be a really poor language for its badness to outweigh having most of the work done for you up front.
If, however, you're starting from scratch on something relatively novel, e.g. where Viaweb was in 1996 (and not so much in 2001), then it's true, you should write in the language that fits the bill rather than following the course of momentum.
One proviso I would add there though is that Lisp is in the position of being fairly mature and non-traditional, unlike many flavor-of-the-weeks. There are many pains to be found in using tools which haven't stabilized yet, even if they do have a gee-whiz-bang factor.
As to your postscript, Google does also extensively use C++; I think that's still fairly common in high-performance stuff at the lower levels.
Use (something like) Clojure (or a dot net equivalent)and you can have the best of both - a lisp and lots of libraries. The (minor) price is some grunginess at the interface of the lisp and the libraries, but this is paid only once.
I'm not saying you should write everything yourself, just the bits that matter :)
Sometimes it is quicker to write the exact thing you need rather than struggling with something that wants you to think it is the solution to your problem.
Another case in point was the Aha! moment someone described when realized that the Lisp Postgress interface was not going against the library but against the wire protocol itself. Just as easy.
But I agree. It's a matter of deciding when it matters, and when it doesn't.
In these cases it's to your advantage to use the mainstream tools because there are so many resources available to you.
Libraries tend to be generic, so you can often do better for your specific problem if you are willing to pay the opportunity cost.
I thought GPL libs could be used n a web based project? PG's article says (emphasis mine)
"One of the reasons to use Lisp in writing Web-based applications .. "
(Also, what is with all the anti-GPL FUD on this site? Have any of you guys read the license, or do you just like to bash it because you don't like Free Software?)
"When you're writing software that is only going to run on your own servers, you can use whatever language you want."
If you're not distributing software then the GPL doesn't apply. A web-based start up can use as many GPL-based libraries as they want.
On many projects this isn't as much of a problem, but I think it's dangerous to assume that one can easily use 'any language' when developing web-based software.