Hacker News new | past | comments | ask | show | jobs | submit login

Nice. New process definitely sounds cleaner if it supports what your program does, but I think if you have open GUI windows or GPU contexts you want to keep around, the dylib route might be your only option.



I don't know about GPU contexts: is there no way to hand them off? Reliable hot reload is always painful no matter how you do it. I don't know the situation with gpu contexts but if your long running program needs hot reloads and has a gui, maybe you want to split the gui itself into a separate process, or alternatively maybe do that with the component requiring reload.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: