Since its inception, Microsoft Excel has changed how people organize, analyze, and visualize their data, providing a basis for decision-making for the flying billionaires heads up in the clouds who don’t give a fuck for life offtheline

  • nalyd@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    1 year ago

    I think you’re missing that all interpreters have a compilation step that produces machine code, that’s a requirement to produce programs.

    Java’s JIT compiler is the final compilation step of Java’s interpreting path running in a separate thread that turns the intermediate language to machine code. To be very clear though, the output of the standard javac compiler is not machine code that a processor understands. This is what makes Java not a compiled language. It depends on additional processes at runtime to turn the code you wrote into something a processor understands.

    On the performance front, well written Java is fast enough as long as you have sufficient resources for the overhead of JVM and as long as you don’t have strict latency requirements. That makes it good for a pretty wide variety of computing tasks, but, also not a good choice for a lot of others.

    • wolf@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Factual errors:

      • Interpreters neither need nor usually have a compilation step
      • Even processors are nowadays virtual machines, modern hardware only understands microcode AFAIK

      Words which have a common understanding in the current compiler construction world, which you define in IMHO a non standard way

      • Compiler is commonly used to refer to tools which translate higher level languages (e.g. Java, C, Python, JavaScript) to a machine representation (e.g. JVM, Arm64, x86_64, MIPS…)
      • Even in academia Java is referred to as compiled/interpreted language (at the same time)

      Factual errors about Java:

      • We have ahead of time compilers for a very long time now (GraalVM etc)
      • There are chips which implement the JVM in hardware
    • Aceticon@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I think you’re used to modern interpreted languages and are unaware of how the runtimes of interpreted languages used to work.

      Something like Basic (to use a properly old example) was constantly interpreting source code during the entire run.

      If I’m not mistaken Python was the first major interpreted language which by default interpreted the code into a binary format and then just ran the binary (and, if I remember it correctly, that wasn’t the case in its first version). By this point Java already JIT compilation in its VM for a while.

      I think you’re committing the error of comparing modern interpreted languages with how Java worked 2 decades ago.