Compiled code is fast, interpreted code is slow. There is not much we can do about it, and it's the reason why interpreters' use in high performance computing is usually restricted to job submission. We show where interpreters make sense even in the context of analysis code, and what aspects have to be taken into account to make this combination a success.