3 ms·
> With Go that's much more work to get up and running. Can you expand on that? Go is very fast to get up and running, you DL go runtime, git clone a repo, go b
by Thaxll 8y ago
> With Go that's much more work to get up and running.
Can you expand on that? Go is very fast to get up and running, you DL go runtime, git clone a repo, go build . and have your single executable ready to go.
- tschellenbach 8y agoThis bit of Phoenix: https://phoenixframework.org/blog/the-road-to-2-million-websocket-connections https://phoenixframework.org/blog/the-road-to-2-million-webs... Takes substantially more work in Go.
- Thaxll 8y agoThanks for the answer, for Go it doesn't take much most likely easier than in Erlang: http://goroutines.com/10m http://goroutines.com/10m I never had to work on that many connections per instance, but knowing how much faster Go is vs Erlang I woudn't see this as an issue?
- joevandyk 8y agoHe's referring to Go being more work to setup realtime web things, as opposed to Phoenix.