Golang is minimalism, as a developer you can just focus on the engineering aspects and not worry about clunky build tools, importing 3rd party packages and so forth.
Most of what you need is built into the standard library so you don't need to reach for third-party code that often.
Golang compiles and runs incredibly fast, so very easy to scale without much effort. Furthermore, goroutines and channels are just so seamless to work with. To deploy, you literally just build and replace the binary, you don't need a process manager or other service to manage your application. It's fully self-contained.
One of the most annoying things in Node is that most things are async by default, In Golang it's the opposite. You only use concurrency when needed.
Typing in Golang is a breeze, it's not as weird as TypeScript and feels natural.
Lastly, this is debatable but I think the error handling is pretty cool too. Instead of having hundreds of try-catch blocks everywhere, you simply return an "error". The caller can then check for errors and handle those accordingly.
Ultimately it comes down to you as an individual, while there are better tools for certain tasks, generally, most modern stacks are good enough to handle most workloads. So I would just stick with what I know unless there's a clear reason to switch.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Golang is minimalism, as a developer you can just focus on the engineering aspects and not worry about clunky build tools, importing 3rd party packages and so forth.
Most of what you need is built into the standard library so you don't need to reach for third-party code that often.
Golang compiles and runs incredibly fast, so very easy to scale without much effort. Furthermore, goroutines and channels are just so seamless to work with. To deploy, you literally just build and replace the binary, you don't need a process manager or other service to manage your application. It's fully self-contained.
One of the most annoying things in Node is that most things are async by default, In Golang it's the opposite. You only use concurrency when needed.
Typing in Golang is a breeze, it's not as weird as TypeScript and feels natural.
Lastly, this is debatable but I think the error handling is pretty cool too. Instead of having hundreds of try-catch blocks everywhere, you simply return an "error". The caller can then check for errors and handle those accordingly.
Ultimately it comes down to you as an individual, while there are better tools for certain tasks, generally, most modern stacks are good enough to handle most workloads. So I would just stick with what I know unless there's a clear reason to switch.