By iffycan
As feedback on the article itself, I kept getting confused. The author describes a wish:
> If I write a function to sum a list of numbers, it would be nice if I could use it on lists of floats, lists of ints, and lists of anything else that can be summed.
I agree with the author and continue reading, expecting to see an implementation of that function in each language. I keep reading and re-reading to try to figure out how the first two code samples (Rust and Haskell) are summing a list. I feel like an idiot, because I can’t figure out how that code is possibly summing a list. Thankfully, the next paragraph explains it, but a heads up would have made it more clear.
The article continues with pairs of Rust and Haskell — as a reader, I’m thinking, “Yes, yes, but show me how this compares to Go.” Finally, when I get to `Go’s Solution: interface` I feel like I’ll be able to compare the languages… but instead of implementing an already-mentioned problem, a new problem is introduced:
> Let’s say you wanted to write a function that printed a hash code for objects that could be hashed.
As a reader, I have too many things in my head now.
I think the author probably has valid points to make, and I will now finish reading the article. Hopefully some of this feedback is helpful (I’m not trying to be a jerk).
Read more here: https://news.ycombinator.com/item?id=10704729
iffycan comments on "Why Go Is Not Good"
No comments:
Post a Comment