2 ms·
This is awesome. Back in the day, writing cross-platform code meant knowing the ins-and-outs of each platform you wanted to support and coding specifically for
by mholt 12y ago
This is awesome.
Back in the day, writing cross-platform code meant knowing the ins-and-outs of each platform you wanted to support and coding specifically for each one. Interpreted languages (like Python) and runtimes (like JRE) take a lot of the pain away, but that means all those programs have a dependency: the interpreter or runtime.
Go isn't interpreted and bundles its runtime inside the executable. That has always been pretty great, but with Go 1.5, the programmer won't even have to run `env GOOS=... GOARCH=... make.bash --no-clean` before compiling for another platform.
With veteran OS and systems engineers working on the language, this is why we can have nice things.
- pjmlp 12y ago> Back in the day, writing cross-platform code meant knowing the ins-and-outs of each platform you wanted to support and coding specifically for each one. If you mean C and C++ POSIX behavior, yes. If you mean native languages with rich runtimes like Ada and Modula-2, not really. Finally Go doesn't get rid of OS specific stuff like pathnames, security, ...