Will Go become “full-stack?”
I cannot speak for the Go team.
However, I can read the tea leaves. In my estimation — based on the past 10+ years — I would say there is less than a 1% chance the Go team has any plans to optimize Go for front-end development, other than to support WebAssembly.
But hey, I could be wrong!
Why use Go vs. Node?
Why build backend and front-end in different languages? It lets you use the best tool for each job.
Avoid Dependency Hell
Further, you don’t have dependency hell in GoLang anywhere near the way you do with Node; no
node_modules directory with an infinite number of files and directories (I exaggerate. Well, only a little):
This blog post from a member of the Go team explains in detail why Node dependency management is such as problem and why GoLang is so much better (Note: Read the whole post, not just these headline because reading only the headline might give you the wrong impression of what the problem is.)
Different folks, different strokes
For me, life is so much nicer now! And the pay is a lot better, too.
So it’s up to you to choose what you want. Sibert and I tag-teamed to answer your questions and we’ve given you plenty to go on; now the choice is yours.
P.S. A 3rd Option
Again, hope this helps.