News for hackers. Stuff that matters.
Re:Three Months of Go, from a Haskeller’s perspective (2016) by icebraining on Sunday March 19, 2017 @06:01AM (#13906187)
I don't understand. How can they not be comparable? They're the same type of tool, built with the same goal (writing any kind of software). In fact, Go itself was born because its creators felt the current languages weren't good at handling the current computing environment - comparisons with other languages are the at core of its existence. Finally, why even choose Go if it's not because it has some comparative advantage? Might as well stick with what we already know.
Re:Three Months of Go, from a Haskeller’s perspective (2016) by cube2222 on Sunday March 19, 2017 @07:40AM (#13906512)
They're not the same type of tool. Go is mainly aimed at distributed computing evironments and infrastructural tools. I really don't see a sensible Consul/Kubernetes/Docker alternative being written in Haskell.
Re:Three Months of Go, from a Haskeller’s perspective (2016) by dalailambda on Sunday March 19, 2017 @08:08AM (#13906621)
I don't see why not, Haskell has green threads, channels, and everything that Go has. The only argument I can see made is that the laziness and current GC implementation aren't suited, and even then, those problems can be solved with strictness pragmas, and a different GC respectively.
Re:Three Months of Go, from a Haskeller’s perspective (2016) by runeks on Sunday March 19, 2017 @08:14AM (#13906639)

   > I really don't see a sensible Consul/Kubernetes/Docker alternative being written in Haskell.
The only reason for this is the unpredictable latency issues caused by the current garbage collector in GHC. This should be avoidable once GHC has linear types[1] and someone rewrites its GC to take advantage of this.

[1] https://news.ycombinator.com/item?id=13866787