News for hackers. Stuff that matters.
Re:Go hits the concurrency nail on the head by ngrilly on Thursday October 04, 2018 @03:02PM (#18142622)
True, but Go and Erlang don't occupy the same niche.

Go is imperative, while Erlang is mostly functional.

Go is AOT (ahead-of-time) compiled, while Erlang runs on a VM.

Go is statically typed, while Erlang is dynamically typed (I know about Dializer).

Go concurrency primitives are designed to coordinate goroutines living in the same process, while Erlang concurrency primitives are designed to coordinate Erlang "processes" living in the Erlang VM or even in multiple Erlang VMs forming a cluster.

Re:Go hits the concurrency nail on the head by dnautics on Thursday October 04, 2018 @04:25PM (#18143351)
Erlang is AOT, the vm reads compiled and optimized bytecode.
Re:Go hits the concurrency nail on the head by ngrilly on Thursday October 04, 2018 @05:08PM (#18143688)
You're right. I oversimplified a bit too much.

I should have write: Go produces native binaries, while Erlang runs on a VM.

Re:Go hits the concurrency nail on the head by Sharlin on Thursday October 04, 2018 @04:33PM (#18143414)
The point is that Erlang (like Java etc) needs a runtime, Go doesn't.
Re:Go hits the concurrency nail on the head by pjmlp on Thursday October 04, 2018 @04:51PM (#18143556)
Every programming language has a runtime, even Assembly if the CPU is micro-coded.

How do you think that the GC, go-routine scheduler, cgo marshaling get managed?

Re:Go hits the concurrency nail on the head by qznc on Thursday October 04, 2018 @05:07PM (#18143678)
I assume what people want to say is that Go requires nothing which other languages install via the system package manager. While "runtime" is not the correct term, the desire is real.

With Java you first install a JVM. With Python you install the interpreter and batteries. This always leads to version conflicts at some point.

In contrast, with Go your CI builds an executable, you transfer that to your server and it runs. You don't have to care about the version of some "runtime" already on your server.

Re:Go hits the concurrency nail on the head by pjmlp on Thursday October 04, 2018 @05:39PM (#18143905)
Using the wrong terms leads to urban myths and misunderstandings.

You don't need to install Java at all, because the JVM can be bundled with the application, and for anyone that actually cares to pay for them, the large majority of commercial Java third party vendors have AOT compilers on their JDKs.

Likewise with Python, there are several solutions how to bundle a set of scripts with an executable.

Re:Go hits the concurrency nail on the head by brianwawok on Thursday October 04, 2018 @05:26PM (#18143819)
And if you deploy with docker then your build server slaps your java Jar and JRE in a docker image and you deploy one thing. No functional difference.
Re:Go hits the concurrency nail on the head by merb on Thursday October 04, 2018 @05:30PM (#18143846)
well to be fair you can do the same in java, python whatever. it is just not as easy as go install/go build. heck in c# you actually only need to have dotnet runtime >= your higehst installed version. basically I think .net core 2.1+ does it better than any other tools, it can be published via `--self-contained --runtime linux-x64` or without. (the runtime is needed since you create a launcher executable)

it's just dotnet publish with the switch or without and you get a folder that you can copy where you need the runtime or where the runtime + start script is inside the folder.

(Java 9+ has something similar but it's way more complicated than just running java publish, etc..)

Re:Go hits the concurrency nail on the head by weberc2 on Thursday October 04, 2018 @05:20PM (#18143776)
I thought it was pretty obvious that the OP was using "runtime" to refer to an external interpreter program. The significance being the simplicity of deployment.
Re:Go hits the concurrency nail on the head by marcosdumay on Thursday October 04, 2018 @08:53PM (#18144871)
I didn't think it was all that obvious, and after I read the OP's answers I thought he was complaining about distributable size, instead of deployment procedures.
Re:Go hits the concurrency nail on the head by pjmlp on Thursday October 04, 2018 @05:35PM (#18143882)
That is an interpreter as you very well mention.
Re:Go hits the concurrency nail on the head by weberc2 on Thursday October 04, 2018 @06:04PM (#18144081)
Sometimes things have multiple names :shrug: I really like your contributions; this one seemed unnecessarily pedantic.
Re:Go hits the concurrency nail on the head by pjmlp on Thursday October 04, 2018 @06:07PM (#18144103)
Which any CS book clearly clarifies.