A very interesting post by Brian McCallister on the best possible dynamic language to use in a multi-threaded Apache HTTP environment. The problem, in his own words:
The basic problem, in my opinion, is that ruby (and python) both like to be the language. You extend them, you don’t embed them. You use ruby to drive C, not C to drive ruby. Extending ruby is fun and easy. Extending httpd with ruby is pain. Anything can be worked around, of course, but it feels like just that, work. You are fighting the grain of the problem, and basically using a great general purpose web server and application platform as an HTTP scrubber, cache, and static resource server.
He’s found a few languages that work differently:
He finally settled for Lua. Yet another entry in my ever-growing list of things to take a look at. Sigh.