It's good to see this happening, and happening in the open. In both JS and Python I've seen GraphQL execution take a ridiculous amount of time using the commonl

It's good to see this happening, and happening in the open. In both JS and Python I've seen GraphQL execution take a ridiculous amount of time using the commonly used libraries, so long that we had fall back to raw JSON content in some parts of our schema that previously had a lot of small resolvers. There was a Python semi-JIT experiment a while ago, but it was paid and had some dodgy security implications os we couldn't use it, but the concept is a strong one. This has been an effective approach for other areas like templating in Jinja2, so I'm not surprised that it's being used for GraphQL.