Re:Hot Reloading in Swift
by dmix on Thursday July 14, 2022 @06:37PM
(#32102225)
Erlang has had hotloading for a long time and seems to be fine security wise AFAIK.
[ Parent
| on HN ]
Erlang has a very limited security model. In the default distribution, any process on any node can spawn a process on any other connected node to run any function --- you can send the function too. Modules can have a function to run on load, too. Loading an untrusted module is asking for that module to take over your whole system. Best to make sure nobody unauthorized can do that.
Hot reloading’s quality (and to a degree, security) depends mostly on how fine-grained a change can be. The reason Lisp-REPl workloads are so well loved is that very small scopes can be changed easily, Erlang also has a sane encapsulation that can be swapped without much fuss.
Re:Hot Reloading in Swift
by jjtheblunt on Thursday July 14, 2022 @08:20PM
(#32103005)
just wanted to say i really like the clarity of that explanation