It's quite astounding that architectures their size are implemented with the "slowest language around". It would be very interesting to read in-depth how they manage to sidestep the performance problems (that are brought up almost always when someone mentions Python).
My biggest problem though isn't which scripting language someone should use for some task. It's getting them to the idea that they should use a scripting language for some task.
People forget that HN is not the norm.
Anyway, I've seen people opening sockets in Prolog, and I've seen people doing artificial intelligence in C.
It's not about optimization, but it's surely possible to pick the wrong language for a task.
Nothing prevents anyone from writing their Java builds in, say, Python (shelling out to javac when needed) but no one does and with a good reason.
What's the reason?
People like to do premature optimization, and choosing the language is one way.
People love to take that quote that was talking about a very specific thing and use it to justify not thinking about performance at all.
Because algorithm improvements can dramatically exceed execution time improvements, working in a language that facilitates rapid development and iteration is a path to better final performance than early optimization for execution speed, which is then difficult to modify.
That said, premature coding is also a negative - it pays to evaluate and refine the algorithm before coding - but sometimes executable pseudocode helps in that process.
Far too many programmers simply don't know ANY scripting languages. So the concept that they might want to write a quick script to do some task is simply not in scope AT ALL.