You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hot reloading is always a pit tricky. The programming model needs to explicitly support it. In lunatic it will consist of 2 parts:
Stuff inside the vm that lets you keep the process id and message queue, but replaces the code running.
Higher level libraries that allows you to preserve state when the code is reloaded and potentially do state modification so that the newly loaded code can continue operating on the existing state.
This is fairly similar to how Erlang does it and I think it's a good approach for most use cases. However, currently we are stretched a bit thin and nobody is working on it. It's hard to predict when it will land.
To your other questions, I would say it's already a good replacement for some Erlang use cases. Lunatic should be faster in compute intensive workloads, but you would still need to benchmark to make sure it's actually faster :)
great work!
The text was updated successfully, but these errors were encountered: