Did you read the comments at the links you list? People are saying that Common LISP was doing both at the same time in the 80s. One of them even describes what can go wrong when you do it badly.
Here's just one of many:
Common Lisp can change pretty much anything at run-time. If you redefine a class to have fewer or more slots, the existing instances of those classes will have some problems.
Another:
There are Forth systems that can do this as well. You have to manage everything yourself and your code might not work or be compiled to native code on other systems, but this is true of everything else in Forth.
Erlang also has hot code loading with versioned code and precise and easy ways to migrate processes from old to newer code, and with HIPE you get native code (but not compact executables) on some architectures.
The presentation's interesting, but the title only furthers the non-goal of making people talk about Common Lisp.
Hey, a while back I wrote an article on this subject: https://16bpp.net/page/hot-loading-code-in-nim
Neat work you've done though.
Did you read the comments at the links you list? People are saying that Common LISP was doing both at the same time in the 80s.
That's why the thread title is in quotes - this is something we can discuss and qualify.
Maybe the exact language of the claim needs to be altered, but I'd like to see examples. Please note all details of the claim ― "First natively compiled language with hot code-reloading at runtime":