3 ms·

Byte Code and VMs are are older than just 90's tech but okay. I still honestly prefer native code, but it does not work well for non-open source software unless

by anfilt 5y ago

Byte Code and VMs are are older than just 90's tech but okay. I still honestly prefer native code, but it does not work well for non-open source software unless the developer also compiles for other systems. Also windows is really the only major non-*nix OS these days. Although apples GUI software stack is still a pain port for when porting.

015a 5y ago
Sure, its 20s tech (WASM), 10s tech (Web/PWA), 00s tech (Java), 90s tech (Java), 80s tech (Erlang/BEAM), jeeze even 50s tech (Lisp)... There are people who complain about how the industry is moving in cycles and how what's old is new again and how functional languages did that back in 1922. These people don't change the world; they just complain about how other people are changing it.
- anfilt 5y ago
  Huh? I don't see how what I was saying was complaining? Sure things sometimes happen in cycles, I did not even mention that, but it is not necessarily a bad thing. VMs, and byte codes are a tool, and have their place. However, they do have their limitations compared to natively compiled code.
  - pjmlp 5y ago
    Like? Just because it is bytecode it doesn't mean it is interpreted. > Unlike some other virtual-machine architectures in which the virtual instructions are interpreted at run time, TIMI instructions are never interpreted. They constitute an intermediate compile time step and are translated into the processor's instruction set as the final compilation step. The TIMI instructions are stored within the final program object, in addition to the executable machine instructions. This is how application objects compiled on one processor family (e.g., the original CISC AS/400 48-bit processors) could be moved to a new processor (e.g., PowerPC 64-bit) without re-compilation. An application saved from the older 48-bit platform can simply be restored onto the new 64-bit platform where the operating system discards the old machine instructions and re-translates the TIMI instructions into 64-bit instructions for the new processor. From https://handwiki.org/wiki/IBM_System_i https://handwiki.org/wiki/IBM_System_i

by anfilt 5y ago

015a 5y ago

Sure, its 20s tech (WASM), 10s tech (Web/PWA), 00s tech (Java), 90s tech (Java), 80s tech (Erlang/BEAM), jeeze even 50s tech (Lisp)... There are people who complain about how the industry is moving in cycles and how what's old is new again and how functional languages did that back in 1922. These people don't change the world; they just complain about how other people are changing it.

anfilt 5y ago
Huh? I don't see how what I was saying was complaining? Sure things sometimes happen in cycles, I did not even mention that, but it is not necessarily a bad thing. VMs, and byte codes are a tool, and have their place. However, they do have their limitations compared to natively compiled code.
- pjmlp 5y ago
  Like? Just because it is bytecode it doesn't mean it is interpreted. > Unlike some other virtual-machine architectures in which the virtual instructions are interpreted at run time, TIMI instructions are never interpreted. They constitute an intermediate compile time step and are translated into the processor's instruction set as the final compilation step. The TIMI instructions are stored within the final program object, in addition to the executable machine instructions. This is how application objects compiled on one processor family (e.g., the original CISC AS/400 48-bit processors) could be moved to a new processor (e.g., PowerPC 64-bit) without re-compilation. An application saved from the older 48-bit platform can simply be restored onto the new 64-bit platform where the operating system discards the old machine instructions and re-translates the TIMI instructions into 64-bit instructions for the new processor. From https://handwiki.org/wiki/IBM_System_i https://handwiki.org/wiki/IBM_System_i