Ironically, I think Brad Cox had something like this in mind, after coming up with Objective C. Or at least, pluggable components [1]<p>I wonder what the threat model would be? Injectable binaries seem like a decent attack vector. But, if we're talking 2040, maybe a signable Merkle tree would do the trick.<p>Meanwhile, have been experimenting with recompiling Metal code at runtime. Was kinda fun with ObjC/C++/OpenGL, a few years ago.<p>[1] <a href="https://thenewstack.io/objective-cs-roots-in-the-life-of-brad-cox/" rel="nofollow">https://thenewstack.io/objective-cs-roots-in-the-life-of-bra...</a>
This is one of the main reasons I like Common Lisp, and Clozure CL in particular, which has a blazing fast compiler: my debug cycles are measured in seconds. Over dozens or hundreds of cycles it really adds up.
You can hot-reload any language that can load a dynamic library. Compile the hot-reloadable portion of your app to a dylib and use a hotkey to reload the lib.
"Microsoft has been killing it over the last decade regarding dev tooling and experience, so it is not a big surprise."<p>To be fair, for all the flack Microsoft got/gets, the dev tooling for Windows ecosystem is miles ahead of anyone else and world class. Perhaps I am biased as I worked there at one point, but since I don't anymore, I have also seen tooling from Apple and Google and they are a couple of decades behind. There is some truth to why Steve Ballmer went ballistic with his Developer chant, they really built great tooling for developers.