Well, start with one, and ask the question, "Are there any advantages/disadvantages to choosing the other?"
Personally, I find the mindset of the Go community to be wary of pulling in unnecessary dependencies, and favor writing it yourself, of perhaps copy/pasting some methods from a popular library, rather than depending on it. I also find more experienced developers preferring Go.
Node, on the other hand, seems to prefer pulling in whatever dependency has 1 method the developer would like to use, without any thought to how that will affect other developers, and/or the overall project.
All the above is purely anecdotal, of course, but I am genuinely interested in any sort of empirical data that supports a single advantage that Node has over Go; it's certainly not performance, time to develop, readability (subjective), documentation, community...Well, start with one, and ask the question, "Are there any advantages/disadvantages to choosing the other?"
Personally, I find the mindset of the Go community to be wary of pulling in unnecessary dependencies, and favor writing it yourself, of perhaps copy/pasting some methods from a popular library, rather than depending on it. I also find more experienced developers preferring Go.
Node, on the other hand, seems to prefer pulling in whatever dependency has 1 method the developer would like to use, without any thought to how that will affect other developers, and/or the overall project.
All the above is purely anecdotal, of course, but I am genuinely interested in any sort of empirical data that supports a single advantage that Node has over Go; it's certainly not performance, time to develop, readability (subjective), documentation, community...