5 ms·

This is a good article. I am curious how the author compiled it. Everytime they came across a quirk they'd log it in a journal? Fun :) Figured I'd comment on a

This is a good article. I am curious how the author compiled it. Everytime they came across a quirk they'd log it in a journal? Fun :) Figured I'd comment on at least one item which I ran into recently. > Sends and receives to a nil channel block forever. This did feel bizarre to me too, until I realized how well this works with select blocks. That IMO, is the primary justification for that design choice.

tedunangst 4y ago
> During this time, I’ve been making notes of speed bumps I’ve run into, as well as things I’ve liked about Go. This is a smart approach to a new language. Especially since you now have a list of things to recheck your early code for.
- rob74 4y ago
  ...as long as you make an honest effort to understand why things you don't like are the way they are and don't just think "hey, cool, I found another thing to add to my list of things I don't like about Go!". Go is very opinionated and does some things differently from the mainstream. So you'll have to adapt your programming style in order to use Go successfully. Developers who aren't flexible enough will most likely hate it.