4 ms·
Maybe you are building a standalone utility in Go that can be downloaded as a single binary. Great. Most places I work at, deploy to Kubernetes as docker contai
by eweise 4y ago
Maybe you are building a standalone utility in Go that can be downloaded as a single binary. Great. Most places I work at, deploy to Kubernetes as docker containers
- coldtea 4y agoGiven that the context on this subthread is how a benefit from Go is that it "compiles to a single executable that's easy to deploy. This is a compelling advantage over Java,C#,Python,Ruby that require runtimes or complicated virtual environments." I fail to see how this information about "most places you work for" is relevant. Even if that's the case, you can always also deploy Go with kubernetes and whatever. But you can't deploy most of the others as a single static binary. (Getting one out of Java, for one, requires some half-arsed non-really-supported solutions, whereas getting one out of Go is the default).
- eweise 4y ago"I fail to see how this information about "most places you work for" is relevant." I can spell it out. Where is I work is a web based business and those businesses are typically using hosted environments. Go binaries aren't an advantage in these environments.
- coldtea 4y agoOne can, and many do, just deploy a single Go binary into those "hosted environments". There have been a couple of posts on HN of teams doing that. In fact one can even do it your way, and use kubernetes and co in those hosted environments and Go binaries would still be an advantage -- because the container for the go-based service can just have a static binary inside, and be relatively easier to manage than a Java one.
- eweise 4y agoJava deploys as a single file so would be the same as a Go binary. Container just needs the JVM included, which is trivial.
- pjmlp 4y agoLast time I checked, Go has a runtime as well.
- coldtea 4y agoWhich is neither here nor there. It'a runtime that's run from the statically combined binary.
- pjmlp 4y agoGreat, Java is doing the same since the first commercial JDKs started supporting AOT compilation around 2000. Or if you prefer free beer recipes, gcj which got dropped when most developers eventually moved into hacking into OpenJDK around 2009.
- morelisp 4y agoWhat other people actually use matters a lot though. Hell, a greater proportion of Java devs ca. 2002 probably knew how to AOT-compile their programs than do today. Using minority tooling in a popular language is often just as painful as using a minority language.
- pjmlp 4y agoThat is orthogonal to what language implementations can do, failure to education doesn't change what tools are available.