You got bitten by that but that's not the fault of Go.

The OP was bitten as well and describes a solution in Go. You've solved it by using Node.

Still, your post is quite destructive. Just get over it.

I wonder if anyone has read the linked article?

The overhead of goroutines are well known. The article describes the problem and a solution.

Now someone who got bitten by the overhead of goroutines complains with a (understandable) little bitter tone. He has a good explanation for the issue and why he didn't use Rust but Node.

Citation:

>> I started exploring various options ranging from Rust, Elixir, Crystal, and Node.js. Rust was my second choice, but it doesn't have a good, stable, production ready WebSocket server library yet. Crystal was dropped due to conservative nature of Boehm GC, and Elixir also used more memory than I expected. Node.js surprisingly gave me a nice balance of memory usage and speed.

Then someone didn't seem to have read all the stuff comes around and smartly calls "Use the awesome Rust".

Even as a Rust user myself I get annoyed.