25 ms·
There is a lot of noise in the article (like mentioning Rob Pike's take on syntax highlighting), but mostly it seems to be a "I like Rust and Haskell, and don't
by divan 7y ago
There is a lot of noise in the article (like mentioning Rob Pike's take on syntax highlighting), but mostly it seems to be a "I like Rust and Haskell, and don't like Go" type of articles. Could've been a single tweet.
Attempt to explain the dangers of simplicity is lost in vague sentences like "Rust has different concept of simplicity -> Rust authors wanted to protect from memory errors" or TBU (True But Useless) phrases like "every choice has a cost"/"everything is a tradeoff".
- jolmg 7y ago> mostly it seems to be a "I like Rust and Haskell, and don't like Go" type of articles The mentions of Rust, Haskell, and Go are limited to a single section of the article, so I'm not sure what you're talking about. Most of the article seems to stay abstract with concrete cases brought as examples.
- divan 7y agoI might be biased, as I had to read every Go rant back then when writing a "How to complain about Go" article, and this is clearly the same narrative. Author did a good job to hide it, but if you look closer you'll see indirect Go mentioning throughout the whole article: - "“What do you mean, you think Go’s error handling is bad? It’s simple!”" - How can we articulate a position more powerful than “syntax highlighting is juvenile?” <- refers to the Rob Pike's opinion about syntax highlight - "Go’s error handling has become a meme," - "The creators of Go have said, sometimes in pejorative terms,1 that “average programmers” have difficulty understanding complex languages," - "It’s inflammatory, but the article “Why Go’s design is a disservice to intelligent programmers” is worth reading just for the quotes from Rob Pike."