It's not quite that simple. A different algorithm and/or some well placed caching can easily outweigh the difference between a fast compiled (i.e. probably mor

It's not quite that simple. A different algorithm and/or some well placed caching can easily outweigh the difference between a fast compiled (i.e. probably more efficient) language and slower interpreted one. Obviously, a more efficient language with a better algorithm and good caching is best, but often we don't have the resources (whether it be time or money or whatever) to engineer the best solution, so we need to choose where to focus carefully. Sometimes that means faster prototyping in a language that may not be quite as efficient, and then using the extra time to iterate on algorithmic changes that may yield major benefits or put a caching layer in place.