So, I have a new shiny toy – Go Optimization Guide! And the toy consumes quite a lot of my free time, considering I do not have much. This is a work in progress, and I am actively adding new info there. Why do I believe this is needed? Because even Go doesn’t expose as many opportunities for performance tuning as languages like C++ or Rust, it still provides plenty of opportunities to make your applications significantly faster. At the same time, I do not see anything practical that covers this area. Sure, there’s the go-per-book, but maybe it’s because of my broad C++ background, but I do not think it’s practical enough or easy to read or adopt in real projects. I needed something clear, straightforward, and, I say, enjoyable!
The initial part of my guide is complete and relatively polished based on the feedback I have received. The next step is to develop the networking section because I believe Go is fundamentally about networking apps. Therefore, I’m not planning to post anything here for a while, at least until my new project reaches a reasonable state.