←back to thread

Leveraging Elixir's hot code loading capabilities to modularize a monolithic app

(lucassifoni.info)
73 points ronxjansen | 1 comments | 08 Jul 25 07:14 UTC | HN request time: 0.205s | source
Show context
fud101 ◴[12 Jul 25 08:13 UTC] No.44540240[source]▶
I thought elixir devs have cooled on the whole hot reload update or is this different?
replies(4): >>44540247 #>>44540291 #>>44541102 #>>44541400 #
elitepleb ◴[12 Jul 25 08:25 UTC] No.44540291[source]▶
Elixir removed a jankier https://www.erlang.org/doc/apps/sasl/appup.html mechanism that defined how state is upgraded or downgraded, while watching a directory and recompiling a module automatically or manually from the repl is still common
replies(1): >>44540328 #
diggan ◴[12 Jul 25 08:31 UTC] No.44540328[source]▶
> while watching a directory and recompiling a module automatically or manually from the repl is still common

That makes it sound like the "hot" part has been removed then, and it's just basically a "live reload" rather than "hot code loading", is that right? There is no persistent state and you get a fresh one after the automatic compilation happened?

replies(1): >>44540380 #
1. elitepleb ◴[12 Jul 25 08:42 UTC] No.44540380[source]▶
queued messages stay around in the mailboxes, so no state is lost, but don't get migrated/transformed/versioned via the appup mechanism, unless you opt back into it via libraries for it like https://github.com/ausimian/castle