3 ms·
Go doesn't have single binary deployments either. You need a separate binary for every target platform. Java's use of a VM was intended to get around this restr
by vorg 10y ago
Go doesn't have single binary deployments either. You need a separate binary for every target platform. Java's use of a VM was intended to get around this restriction so that a single jar file would work on any platform, as long as the JVM and libraries were present. Though 20 years ago people would call it "write once, debug everywhere" but perhaps that's not much of a problem anymore.
- weberc2 10y ago> Go doesn't have single binary deployments either. You need a separate binary for every target platform. You're confusing static compilation and portability. Static compilation produces a single binary artifact that can run on the platform for which it was compiled. This doesn't imply that it will run on every (or even any) other platforms--in fact, it's not possible for a single binary to run on every platform.