Re:Three Months of Go from a Haskeller’s perspective (2016)
by kevincox on Wednesday November 04, 2020 @10:06AM
(#24989651)
I agree! If people believe that Go is easy to read because it is simple they must love reading brainfuck as there are only a handful of simple operations!
Re:Three Months of Go from a Haskeller’s perspective (2016)
by tored on Wednesday November 04, 2020 @10:09AM
(#24989674)
In what way are Go modules a train wreck?
Re:Three Months of Go from a Haskeller’s perspective (2016)
by clon on Wednesday November 04, 2020 @10:29AM
(#24989850)
Here is a good start:
https://donatstudios.com/Go-v2-Modules
With the relevant HN discussion: https://news.ycombinator.com/item?id=24429045
I have never gotten it. I find Go code somewhat easy to write, just just give up on trying to be concise or elegant, but not at all easy to read. The excessive boilerplate just makes me feel like my brain does not have the working memory to piece it all together.
The constructs are simple, true, but if you are trying to write anything non-trivial, then simple syntax will not make your problem simpler. It is just expressed in tens of times more lines than in Elixir, Haskell or even PHP. This takes a toll on the reader.
As an example - you can accomplish interesting projects with Lego. And it is easy to get going for sure. But at some point, when you are trying to do something non-trivial, it becomes a hindrance, despite it's simplicity. Hence "I built a life-size XYZ in Lego" becomes impressive in it's own right.
Oh, and Go modules is a story of a train wreck.