Re:Nim – Natively compiled language with hot code-reloading ...
by cmm on Wednesday April 24, 2019 @11:32AM
(#19739395)
I see that at this point in time Smalltalk and Lisp machines have become completely memory-holed (oh wait, Smalltalk & Lisp are interactive, thus "interpreted", thus obviously not compiled! I'll show myself out)
[ Parent
| on HN ]
Re:Nim – Natively compiled language with hot code-reloading ...
by IronBacon on Wednesday April 24, 2019 @05:37PM
(#19742832)
Don't know about Smalltalk but there are numerous CL compilers...
Re:Nim – Natively compiled language with hot code-reloading ...
by hencq on Wednesday April 24, 2019 @07:55PM
(#19743700)
I'm pretty sure that's exactly their point. People assume that interactive means interpreted, but that doesn't need to be the case.
Re:Nim – Natively compiled language with hot code-reloading ...
by IronBacon on Thursday April 25, 2019 @05:06AM
(#19746296)
Ah, my bad, I didn't caught the sarcasm in that post. Yeah, it makes sense now... ^__^;
Re:Nim – Natively compiled language with hot code-reloading ...
by bitwize on Wednesday April 24, 2019 @06:26PM
(#19743185)
Smalltalk is compiled to bytecode.
Re:Nim – Natively compiled language with hot code-reloading ...
by gokr on Tuesday April 30, 2019 @02:31PM
(#19790625)
Smalltalk is a family of dialects and implementations. Most of them are indeed compiled to bytecode which is then executed by a JIT VM. Most of them use the "image" concept where you are always in runtime like in a classic Lisp, and yes, the VM handles shape changes etc etc. But some Smalltalks actually have other characteristics, like non JIT or even compiling via C (Smalltalk/X does that I believe).