The Reliability of Go
andrewwdeane.blogspot.com
The Reliability of Go
1–10 of 144 posts
Re: The Reliability of Go
#2I would like to hear more about the technical implementations from the author on how he managed to improve performance. He mentions: "Due to the complex nature of the system this script could take up to three minutes to scan nodes and process the results" but how does Go solve this complex system that Python couldn't? 3 minutes to 1 second is a superb improvement.
The second paragraph reads like: replacing a relational DB with a (in memory?) key value store resulted in more throughput. He implemented it in Go, but he could have implemented it in any other language.
What I want to know is how he convinced management to use Go? Where did he find the programmers? I work in a similar environment and I don't see my firm adopting Go any time soon, although I wished they had as I'm a big fan of Go and believe it has a place especially server side processes (e.g. algo trading, market data feeds) where concurrent connections are prevalent.
Re: The Reliability of Go
#3"Excellent tooling"; from the article.
What does he mean? I've searched the Go websites but it seems all Google gives you is the Go compiler and a tour.
Re: The Reliability of Go
#4"Excellent tooling"; from the article. What does he mean? I've searched the Go websites but it seems all Google gives you is the Go compiler and a tour.
He is referring to the `go` command, which is a front end to all of go's build tools.
Re: The Reliability of Go
#5"Excellent tooling"; from the article. What does he mean? I've searched the Go websites but it seems all Google gives you is the Go compiler and a tour.
go doc, go fmt, go fix, go vet, go build, go run, go test, go get, go install, ... and present!
Re: The Reliability of Go
#6I would like to hear more about the technical implementations from the author on how he managed to improve performance. He mentions: "Due to the complex nature of the system this script could take up to three minutes to scan nodes and process the results" but how does Go solve this complex system that Python couldn't? 3 minutes to 1 second is a superb improvement. The second paragraph reads like: replacing a relation…
[deleted]
Re: The Reliability of Go
#7"Excellent tooling"; from the article. What does he mean? I've searched the Go websites but it seems all Google gives you is the Go compiler and a tour.
The go command does more than just compile. http://golang.org/doc/cmd
Re: The Reliability of Go
#8I would like to hear more about the technical implementations from the author on how he managed to improve performance. He mentions: "Due to the complex nature of the system this script could take up to three minutes to scan nodes and process the results" but how does Go solve this complex system that Python couldn't? 3 minutes to 1 second is a superb improvement. The second paragraph reads like: replacing a relation…
> He implemented it in Go, but he could have implemented it in any other language
I assume he used Go's concurrency features, although he could have articulated on that.
> Where did he find the programmers
I don't think you explicitly need to hire new programmers. If you have capable, existing programmers, the learning curve is pretty minimal for something like Go.
Re: The Reliability of Go
#9I would like to hear more about the technical implementations from the author on how he managed to improve performance. He mentions: "Due to the complex nature of the system this script could take up to three minutes to scan nodes and process the results" but how does Go solve this complex system that Python couldn't? 3 minutes to 1 second is a superb improvement. The second paragraph reads like: replacing a relation…
> He implemented it in Go, but he could have implemented it in any other language I assume he used Go's concurrency features, although he could have articulated on that. > Where did he find the programmers I don't think you explicitly need to hire new programmers. If you have capable, existing programmers, the learning curve is pretty minimal for something like Go.
>I assume he used Go's concurrency features, although he could have articulated on that.
I've yet to find a good explanation of what is so special about them, why I'd choose it over F# or C# Async/Await.
In the case of pinging servers, I would have prefered to use a 'cheaper' to develop language, which has a boatload of libraries that are widely used.
Anyone got any links or stories about why you would want to use Go for something like that? I don't find this blog story remotely useful in the whole 'why Go' thing.
Re: The Reliability of Go
#10I remember some time ago a complaint about Go having some bugs on 32-bit machines (something related to the GC)
So yes, if you have control over your environment it may be a better choice
But the biggest issue with 'less than mainstream' languages are libraries. Things like DB connectors, protocol libraries (SOAP for example - yes, unfortunately this is necessary for some 3rd part services), etc
Heck, even for Python 2 (not to mention P3) this is an issue sometimes