From the point of view of an application developer you can do pretty much the same things with Node as you can with Go.
So, the change is not worth if Node fit perfectly your application scope.
Even if you use Node successful, you might face some issues while hitting certain limits.
For example, if you write an application that is doing a lot of I/O processing, or you use a huge amount of RAM memory, just to highlight some cases that pop up in my mind.
With Go, you will have a much efficient language, that can help you work on multiple threads, using all the power of modern multi-core CPUs.
Your code in Node can't do that, you need a library in C++ or Rust, that handle the computation for you, or write your code to have different Workers, but this is not as efficient as the Go solution.
With Go you can build executable for many architecture, you just need to provide the target and it will cross-compile.
With Node, you may don't have the issue, if you don't have binary dependencies, but if you end with one of those, you have to set up a build chain that include this target architecture, I mean, you need a VM or a Container Image of this platform to build your application and deploy it.
The list can be longher, but you may get it, there are reason you may choose Go for your task, because with Node you can't be so effective.
In any case, I suggest you to learn Go a bit, even you don't end up using it with your production apps.
Why, because it will help you to refresh your mind with an outside the box approach.
It's good to pich a different language, just for learning purpose, time by time.
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.
From the point of view of an application developer you can do pretty much the same things with Node as you can with Go.
So, the change is not worth if Node fit perfectly your application scope.
Even if you use Node successful, you might face some issues while hitting certain limits.
For example, if you write an application that is doing a lot of I/O processing, or you use a huge amount of RAM memory, just to highlight some cases that pop up in my mind.
With Go, you will have a much efficient language, that can help you work on multiple threads, using all the power of modern multi-core CPUs.
Your code in Node can't do that, you need a library in C++ or Rust, that handle the computation for you, or write your code to have different Workers, but this is not as efficient as the Go solution.
With Go you can build executable for many architecture, you just need to provide the target and it will cross-compile.
With Node, you may don't have the issue, if you don't have binary dependencies, but if you end with one of those, you have to set up a build chain that include this target architecture, I mean, you need a VM or a Container Image of this platform to build your application and deploy it.
The list can be longher, but you may get it, there are reason you may choose Go for your task, because with Node you can't be so effective.
In any case, I suggest you to learn Go a bit, even you don't end up using it with your production apps.
Why, because it will help you to refresh your mind with an outside the box approach.
It's good to pich a different language, just for learning purpose, time by time.