News for hackers. Stuff that matters.
Re:Why Always Docker? by jacques_chester on Sunday January 17, 2016 @08:05PM (#10921944)
> i do wonder what aspects of Go make it good for the container use-case.

Same as JARs or C/C++ binaries. You can ship the compiled product to the target runtime and expect it to launch and run as-is.

Languages with an interpreted nature require containers to also ship an additional runtime, plus a dependencies mechanism.

Re:Why Always Docker? by techdragon on Sunday January 17, 2016 @08:44PM (#10922062)
Go is a step further than these though since it enables "static binaries" you can run go programs in docker with nothing else in their containers. Just one file, the Go binary.

Which is amazing and frustrating since it exposes the inability of other languages to operate in such a simple environment. Even languages like Rust, C and C++ aren't able to do this reliably all the time, with the results being highly dependent on libraries and platforms of choice.

Re:Why Always Docker? by auvrw on Monday January 18, 2016 @02:13AM (#10923030)
thanks for the &replies ;-) ... tbh, Go vs. Rust for the, "i wanna write a Docker-thing!" use case was pretty much the question i had in mind.

the Rust ppl are looking toward static linking [links]...

https://internals.rust-lang.org/t/static-binary-support-in-r... https://github.com/rust-lang/rust-buildbot/issues/24