I'll note that you didn't answer the question. > You keep pushing this idea that this is somehow difficult and takes a ton of time. [...] recompiling it and re

I'll note that you didn't answer the question. > You keep pushing this idea that this is somehow difficult and takes a ton of time. [...] recompiling it and reloading the code isn't an issue No, I didn't. But you can continue trying to move the goalposts, and I will continue pointing out that that's what you're doing. > You say to assume competence and stuff Really? Where? > You've now sort-of redefined what the original problem was to make it seem like hot-reloading shared libraries doesn't solve it. Perhaps you and I have a different understanding of the word "redefined". Or maybe you disagree on what "recompile" means (and/or what it means to say that there is "there is no stop-and-recompile"). I'll (re) ask a simpler question: did you read the post describing TWEAK that I linked to[1]—that is, before you replied (and subsequently dove headlong into trying to change the subject with ad hominem attacks on the competence of the person you responded to)? 1. <https://blog.voxagon.se/2018/03/13/hot-reloading-hardcoded-parameters.html https://blog.voxagon.se/2018/03/13/hot-reloading-hardcoded-p...>