This is the mascot I got at GopherCon2018. To be honest, the Go community is way too cute.

Gopher is a groundhog and the mascot of Go happens to be a groundhog. And then there’s the word “Go,” which is very subtle. All the marmots of the world unite, do you think you can defeat two big snakes?

Go language random thoughts

Full-time use of Go began in mid-2018.

Each language is not good at or bad at. It’s a universal language, which means you can do anything. But in software engineering, “can do” is the basic requirement, “easy to do” and “do well” is the key.

So, in general I’m talking about which language is good or bad to speak, but I’m not saying it’s good in all cases. Not even good in most cases. A language is just a tool. A tool that solves the problem you’re focused on is complete.

Go was originally created to write software for servers, clouds, and backends. So it is destined to outperform many languages in terms of concurrency, memory efficiency, build and deployment. (I’m not going to be very good at this because I don’t speak any languages.)

But instead, it might be metaprogramming, modeling complex business logic (OO?). It’s a little slutty up there.

These two points are hardly in dispute.

However, as a back-end engineer, I am personally willing to trade some language features for overall system performance. Because the features that Go lacks are usually not what I need, the features that Go does well are exactly what I need. It’s all a matter of trade-off.

Therefore, students should consider the characteristics and requirements of the project before choosing the tool when choosing which language to write the project in. Not the other way around. Wouldn’t it be foolish for an engineer to do everything in Python because he only knows Python? Of course, if the time is really too tight, there is no time to do technical investigation and study, that is the last choice. A good engineer, however, needs to do everything he can to avoid “doing what he has to do.”

Go Language Tutorial

Since the first day, I have been slowly collecting and sorting out the Go language learning materials, and also making them myself.

At the beginning, I still focused on videos, but some students suggested whether there could be written materials. I think it’s necessary. However, I’m going to do the hands-on tutorials mostly in video. The article will select some topics or problems to discuss.

There are no articles yet, but if you have any questions, please leave a comment. I’ll try to answer that.

Tutorial links

B station:

Space.bilibili.com/16696495/ch…

Tubing:

www.youtube.com/playlist?li…

Keep an eye on what I’m doing on other platforms

Making:

Github.com/CreatCodeBu…

Wechat Official Account:

B station:

space.bilibili.com/16696495

Tubing:

www.youtube.com/channel/UCH…