The Go HTTP stack is not optimized for raw performance though; there's a number of alternative HTTP stacks written in Go optimized for performance, like fasthttp (https://github.com/valyala/fasthttp). (source: https://www.techempower.com/benchmarks/)

Likewise, the standard library NodeJS http stack will not be as performant as a performance optimized alternative.

That said, if raw performance is your primary concern, neither Go nor NodeJS will be good enough. There's many more factors to consider.

Agreed on fasthttp.

> There's many more factors to consider.

Erlang / Elixir?

nodejs' v8 has millions of man hours spent in optimzation alone since half the internet frontend runs on v8, if not more.

Go being garbage collected and still beating v8 is one hell of an achievement.

If you need faster Go Http you're using the wrong tool.

Go is a statically typed, AOT-compiled language, unlike V8. The kind of task that had countless hours of R&D poured into it for decades, much of it public research and open source code.

I'm not sure how GC is relevant here at all given that JS is also a garbage-collected language.