You can do eval_string/eval_file with EEx too: https://hexdocs.pm/eex/EEx.html - just make sure to pass the EExHTML engine as an option.

If it is for things like blogs, you can cache the result of the rendered template instead.

You don’t need to version it because Elixir modules are versioned in the VM due to hot code reloading. Just keep in mind that this will leak atoms but it is fine if only “admins” can do that.

This is true, but I was hoping to avoid that, because the use case might be different from a blog too. And even blogs have things like comments. It also would not work for partials that are called in loops with different inputs for each iteration.

I can recompile and reload the same module without compiling to a different version first? When do the other processes pick it up, when they make their next call into it? If a compilation error happens, I assume the old version of the module will remain?

Yeah I don’t think people will reload the templates that often, but of course it needs to be measured and taken into consideration, thanks for the reminder.

Immediately on the next fully qualified call to it (ModuleName.function(...)), and yes. Specifically the system keeps around 2 copies of each module that is hot-loaded until no more active references (actively running code) exist to the older one, if there ‘would be’ an even older one than any code actively running it would be killed (and the supervisor would restart it with the new code), but for that to happen in general usage you are either looping manually and near infinitely or you are hot-code reloading new versions extremely rapidly.