Fair enough.
> I expect a modern programming language that has a runtime to not do that, correct.
But how do you define "has a runtime"? Java clearly has one - the JVM. Go produces standalone code, though.
Or do you say that it has a runtime because it has a garbage collector that is running while the program runs?
The original Pascal didn't have a runtime (if you weren't using UCSD, which generated p-code), and yet you couldn't segfault it.
So if I put the jvm and my .jar file inside a single .zip file java no longer has a runtime?
And since C applications load .so files they do have a runtime?
Having a runtime is independent of the amount of files you need to read to run the program.
Fair enough.
> I expect a modern programming language that has a runtime to not do that, correct.
But how do you define "has a runtime"? Java clearly has one - the JVM. Go produces standalone code, though.
Or do you say that it has a runtime because it has a garbage collector that is running while the program runs?
The original Pascal didn't have a runtime (if you weren't using UCSD, which generated p-code), and yet you couldn't segfault it.