Three Months of Go from a Haskeller’s perspective (2016)

Re:Three Months of Go from a Haskeller’s perspective (2016) by greyman on Wednesday November 04, 2020 @02:25AM (#24987028)

I agree with the first sentence, and that I found is one of the strongest points of Go. That you can look at your colleague code and be almost sure what it does, there just aren't hidden traps or clever hacks. It's always the same "dull" code, telling you in plain language what is happening.

[ Parent | on HN ]

Re:Three Months of Go from a Haskeller’s perspective (2016) by ardfard on Wednesday November 04, 2020 @03:08AM (#24987211)

I had an opposite experience. Go code is just like other code in any other languages. It still can be abused to be unholy mess. I see a Go code that have channels all over the place that it's hard to follow the program flow, a function that can panic deep down the stack when feed with certain input.

[ Parent | on HN ]

Re:Three Months of Go from a Haskeller’s perspective (2016) by ghayes on Wednesday November 04, 2020 @03:39AM (#24987345)

Channels for me make Go harder to read than most languages. Once you encounter a channel when reading Go code, good luck understanding the flow from then on.

[ Parent | on HN ]