Hello everyone, I'm back. The past few days were crazy at my work, so many complicated tasks needed to get shipped and I couldn't write here.

Today I'm coming up with a different topic: I don't get the point of Golang - and I need help with it.

Contextualizing things up

Since the beginning of my career, I've always used node in most of my projects, from discord bots to complex backends. I feel a little comfortable with it, but I realized that my way of thinking is becoming tied to this technology.

So, I need fresh air and new things. That's why I want to give Go a chance.

Okay, I get it – when compared to other languages, Go is known for its simplicity and the plethora of benefits it offers. But I don't want to fall into a trap that will solve Go-specific use cases tasks but with a Node mind.

I also don't get the point of it (as the title says). What different or specific things *need * to be done in Go that I can't do with Node?

I want to invite more experienced people, people who have been on the two sides, people who are learning one of these two amazing techs, to join start a discussion here with a main question:

What can I do with Go that I can't do with Node?

Feel free to join in the comments: