6 ms·
This has been my primary objection with Go, as well. I wonder if it's just a lack of practice and that I'd eventually git gud, but I find it so hard to flow thr
by simonsaysso 3y ago
This has been my primary objection with Go, as well. I wonder if it's just a lack of practice and that I'd eventually git gud, but I find it so hard to flow through code to get a general idea of what's going on. It's basically impossible to use code "paragraphs" to separate logical groupings of functionality because of the `if err != nil` blocks, and leads to a very choppy reading experience. With any non-trivial logic, I've found Go to be detrimental to my understanding of what's going on.
- mighmi 3y agoThis seems strange for me, though everyone jumps on this. Most Go projects will use something like: Handle(err) which may take a line, but isn't the 3 lines everyone refers to, and often has a lot of extra logic.