4 ms·
I knew of Smalltalk but was unaware it was 1) byte code rather than compiled and 2) it influences Objective C. Very cool. Seeing also Pascal, Modula, Forth, Pr
by JKCalhoun 4y ago
I knew of Smalltalk but was unaware it was 1) byte code rather than compiled and 2) it influences Objective C. Very cool.
Seeing also Pascal, Modula, Forth, Prolog... The 70's were an innovative era for programming languages. https://en.wikipedia.org/wiki/Timeline_of_programming_languages#1970s https://en.wikipedia.org/wiki/Timeline_of_programming_langua...
- pinewurst 4y agoIt also introduced (in its later ParcPlace form) the idea of JITing interpretive languages.
- pjmlp 4y agoAll Xerox PARC environments (Interlisp, Smalltalk, Mesa, Cedar) were bytecode based, because their CISC CPUs were microcoded. So the first thing a machine would do on boot would be to load the right microcode into the CPU, and then those bytecodes were effectively the Assembly language for the CPU. They were also the genesis of the first JIT compilers, and the OpenJDK Hotspot traces back its heritage to StrongTalk JIT compiler.
- infinite8s 4y agoOne slight difference from current microcoded CPUs is that the end user could implement their own microcode. So each of the systems you mention above implemented their VMs directly in microcode, and as a result tye bytecode became the instruction set for this 'virtual' machine.