The notebook series of "Go Language Actual Combat" is finished, about 30 articles, 15W words. After the end, I started to think about what to write in the next series, or no longer a series, but scattered techniques or cases, etc., but in the end I chose this series of classic library usage analysis of the Go language.
Why did you choose this? This is mainly because when writing the last series, many readers asked them how to use some libraries they encountered, how to solve the problems they encountered, why this is the case, etc., so I found that everyone was right Many libraries are not well understood. I chose this library for the convenience of the project. Although the project can be made quickly, but if you encounter a problem, it is difficult to solve it, because it is someone else’s and I don’t understand it, so I The intention to write this series came up.
An interesting phenomenon, I discovered when I was doing J2EE ten years ago, this phenomenon is that after learning the basics, we like to quickly find some ready-made libraries, frameworks, etc., quickly set up the development environment, and then copy some code , To make some simple things, because it is fast, convenient, fast, and the effect is very good, so there is a sense of accomplishment, and many people go in the wrong direction and become the use of libraries, frameworks and tools. After 5 years, I still have 1 year experience, which is one year of experience in the library I used recently. Those libraries I used before are outdated and useless, so experience Zero.
After I discovered this problem ten years ago, I did not pay so much attention to the use of tool framework libraries. Instead, I accumulated the Java foundation and studied the source code of the framework. At that time, the Spring source code was really a line-by-line look, but I didn’t understand it. I bought the Spring source code to reveal the secrets and looked at it. After learning a framework, I understand the principles and design architecture and ideas. Looking at the others, they are similar. Even if there is a new framework, you can get started quickly. , And quickly become familiar with his principles, and can solve difficult problems.
This is also one of the principles that I studied the use and principles of Go libraries, and accumulated and released this series. Not only do I need to use these libraries, but also understand their principles, design ideas and architecture, learn the essence of them, absorb and grow my own Skills, knowledge, learned, and principles, you can write a good framework by yourself.
Before writing this article, I have not studied too many Go language libraries or frameworks, nor have I accumulated articles, so for myself, this is also an opportunity to learn. It is also possible to gather the strengths of a hundred families and integrate them. Improve my Go language technical ability, that is to say, I will study with you, if there is something wrong, you are welcome to discuss and correct.
The Go language classic library will contain many of the classic Go libraries we use now, such as Beego, Xie Da’s classic, echo, gin, mux, etc., but we will select some simple libraries for analysis in the previous series. , From the shallower to the deeper, accumulate knowledge and skills, and gradually analyze large and complex libraries.
The writing frequency is generally one article a week. There is no way. I can’t usually write. I can only write after 10pm or on weekends. One article per week will be guaranteed. Some of the articles will be longer, and I hope that everyone can read each article without losing a word, so that we can better understand the context and have a deeper understanding.
Finally, if everyone feels good, just share it in the circle of friends, like more, leave a message, share more, it is the greatest support for me, OK, just nag so much, ready to start learning and analyzing Go with everyone Classic library of languages.