Announcing Python in Excel: Combining the power of Python and the flexibility of Excel.
techcommunity.microsoft.com
Since its inception, Microsoft Excel has changed how people organize, analyze, and visualize their data, providing a basis for decision-making for the..

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

    • Phrodo_00@lemmy.worldEnglish
      91·
      1 year ago

      If you go that detailed, then the jvm is JIT compiler, not an interpreter, so Java code still mostly runs natively on the processor. Java is quite fast achieving pretty close performance to C++, the only noticeable problems are on desktop because of the slow jvm startup and slow GUI libraries compared to native ones.

        • wolf@lemmy.zipEnglish
          6·
          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
        • Phrodo_00@lemmy.worldEnglish
          11·
          1 year ago

          all interpreters have a compilation step that produces machine code

          Very much not a thing. JIT interpreters are actually not that common. Most interpreters parse code to an AST in memory and then run execute said AST, without any compilation to machine code.

          the output of the standard javac compiler is not machine code that a processor understands. This is what makes Java not a compiled language.

          Listen to yourself the output of the compiler makes it not a compiled language. Java is a compiled language, and jvm bytecode can be compiled (see graalvm), or interpreted (and when interpreted it can be JITd)

        • Aceticon@lemmy.worldEnglish
          11·
          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.

    • Aceticon@lemmy.worldEnglish
      5·
      1 year ago

      There is another compilation step inside the Java Virtual Machine which “compiles” the VM Assembly code to native code at runtime.

      This is what’s called JIT compilation and has been part of the standard Java Virtual Machine for about 2 decades and the default - at least server side - for almost as long (i.e. you have to explicitly pass a parameter to disable it at startup if you want the old runtime interpreted VM opcode behaviour).

      Source: I used to design and develop mission critical high performance distributed server systems in Java for banks since before 2008 and it definitelly is capable of handling it (the bottleneck tended to be the TB-size database, not the Java application).