46     This compiler is used when code is changed within the running IDE or application.

    46     This compiler is used when code is changed within the running IDE or application,

    47     It generates bytecode methods, which are further translated to machine code by the VM,

    47     and when source code is loaded.

    48     when first executed. 

    48     It generates bytecode methods, which are (typically) further translated to machine code by the VM,

    49     This is not to be confused with the stc-compiler, which generates plain machine code, which

    49     when first executed 

    50     is packaged in compiled class libraries. Usually, end user applications are deployed as 

    50     (although for some architectures, no JITTER is available, and the bytecode will be interpreted, 

    51     stc-compiled binary code. And only patches or dynamically generated code uses bytecode methods.

    51      which is of course much slower).

    52      

    53     This is not to be confused with the stc-compiler, which generates plain machine code, 

    54     which is packaged into compiled class libraries and runs with very good performance. 

    55     Usually, end user applications are deployed as stc-compiled binary code. 

    56     And only patches or dynamically generated code uses bytecode methods.

    57     Therefore, the speed of the bytecode interpreter is usually not at all relevant to a deployed app's 

    58     overall speed (and also not to the ST/X IDE itself, as it also consists of precompiled machine code).