Re:Making the move from Scala to Go
by lazyjones on Wednesday January 25, 2017 @06:01AM
(#13480388)
I found the Go solution for that issue a bit odd - channels aren't for data processing, they're synchronisation primitives. Using them the way they did in the article ruined the piece for me, since it reads like a rather uninformed decision now.
[ Parent
| on HN ]
Are you sure they aren't intended for data processing? I've never heard that claim before, and the Go documentation seems to have a lot of examples of using channels in that way. (https://blog.golang.org/pipelines, for example; or https://tour.golang.org/concurrency/2).
Let me rephrase: not suitable for large amounts of data that need high throughput. It's easy to see that the overhead is prohibitive for applications such as in the article, if you just benchmark it.
https://groups.google.com/d/msg/golang-nuts/LM648yrPpck/tv40...