4 ms·

I mean that’s basically the JVM, isn’t it?

by phyrex 7y ago

antoncohen 7y ago
There was JavaOS: https://en.wikipedia.org/wiki/JavaOS https://en.wikipedia.org/wiki/JavaOS
- vygr 7y ago
  https://en.wikipedia.org/wiki/Virtual_Processor https://en.wikipedia.org/wiki/Virtual_Processor Taos articles link at the bottom, Byte, IEEE, Edge etc.
DannyB2 7y ago
Yes. As a long time Java developer. But the UCSD p-System was much earlier (and more primitive) than Java. p-System never did JIT. Remember this was for machines with 64 K of memory. Not 64 MB. But 64 K! The p-Code was much more compact than native code. Interpreting most code was plenty fast for most things -- even on the slow (under 10 MHz) clock speeds of the era. Critical operations could be written in assembler. The p-System had its own assembler for native code. JVM is a whole other world. Adding GC is a whole new dimension in complexity. But decades of research have gone into the JVM making it the amazing runtime platform it is today.
- pjmlp 7y ago
  There were toolchains that did compile P-System into native code though. https://en.wikipedia.org/wiki/Pascal_MicroEngine https://en.wikipedia.org/wiki/Pascal_MicroEngine https://en.wikipedia.org/wiki/Corvus_Systems https://en.wikipedia.org/wiki/Corvus_Systems Adding a GC to bytecode systems, is what Xerox PARC did with their Interlisp-D, Smalltalk and Mesa/Cedar workstations. The CPUs were microcoded and as part of the boot process they would load the respective hardware interpreter for the environment being booted into the workstation. A similar idea was explored in one of Oberon's implementations, where instead of using straight native code like on the Ceres workstation, the modules would have a compact representation, JITed into native code on module load. See section 7, Machine-Independent Mobile Code on http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.90.7173&rep=rep1&type=pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.90....
  - DannyB2 7y ago
    I remember Corvus quite well. (I've been doing this job for a _loooong_ time.)

I mean that’s basically the JVM, isn’t it?

by phyrex 7y ago

I mean that’s basically the JVM, isn’t it?

antoncohen 7y ago

There was JavaOS: https://en.wikipedia.org/wiki/JavaOS https://en.wikipedia.org/wiki/JavaOS

vygr 7y ago
https://en.wikipedia.org/wiki/Virtual_Processor https://en.wikipedia.org/wiki/Virtual_Processor Taos articles link at the bottom, Byte, IEEE, Edge etc.

DannyB2 7y ago

Yes. As a long time Java developer. But the UCSD p-System was much earlier (and more primitive) than Java. p-System never did JIT. Remember this was for machines with 64 K of memory. Not 64 MB. But 64 K! The p-Code was much more compact than native code. Interpreting most code was plenty fast for most things -- even on the slow (under 10 MHz) clock speeds of the era. Critical operations could be written in assembler. The p-System had its own assembler for native code. JVM is a whole other world. Adding GC is a whole new dimension in complexity. But decades of research have gone into the JVM making it the amazing runtime platform it is today.

pjmlp 7y ago
There were toolchains that did compile P-System into native code though. https://en.wikipedia.org/wiki/Pascal_MicroEngine https://en.wikipedia.org/wiki/Pascal_MicroEngine https://en.wikipedia.org/wiki/Corvus_Systems https://en.wikipedia.org/wiki/Corvus_Systems Adding a GC to bytecode systems, is what Xerox PARC did with their Interlisp-D, Smalltalk and Mesa/Cedar workstations. The CPUs were microcoded and as part of the boot process they would load the respective hardware interpreter for the environment being booted into the workstation. A similar idea was explored in one of Oberon's implementations, where instead of using straight native code like on the Ceres workstation, the modules would have a compact representation, JITed into native code on module load. See section 7, Machine-Independent Mobile Code on http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.90.7173&rep=rep1&type=pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.90....
- DannyB2 7y ago
  I remember Corvus quite well. (I've been doing this job for a _loooong_ time.)