> It's pretty standard for "no runtime" to mean nothing on the device you install the compiled target app.
Only by layman that don't understand compilers.
> It's pretty standard for "no runtime" to mean nothing on the device you install the compiled target app.
Only by layman that don't understand compilers.
The tone here is a bit rude but I'm still curious: what does no runtime mean to you?
It is my tone, GenX, no minced words.
The infrastructure required to support a programming language, startup and shutdown boilerplate, all the required functionality to support standard library features including integration points between language semantics and support code.
Stuff like what code runs before and after main(), trap handlers for floating point arithmetic, handling of thread local storage, bind language heap handling primitives to library code, traps for handling stack overflow errors,....
Right, runtime is so broad that it's hard to say something has "no runtime". libgcc + your choice of crt0 is a C runtime, and the JVM is a Java runtime. That's a huge spectrum.
It's worth being charitable in your interpretation though and recognising "no runtime" probably refers to JVM-shaped or Node-shaped things, not libgcc+crt0-shaped things.
Alternatively, "runtime" is a derogatory term used by programmers who want to show superiority over others who use languages with more (built-in) features than theirs.
There's practically no difference for the overwhelming majority of software these days. Most people aren't working on embedded systems or operating systems.