Rust vs. Go
well actually he says that DNS lookups etc needs to be asynchronous, but aren&#x27;t go&#x27;s channels blocking?<p>I mean he also says that rust has no good epoll&#x2F;select abstraction, which is wrong.
And also &quot;a welter of half-solutions in third-party crates but describe no consensus about which to adopt&quot;
I think he didn&#x27;t researched well enough.<p>I mean it would be the same as saying that there is no good way to create a custom non blocking dns server with pure java&#x2F;scala (no external library used).
Rust has <a href="https:&#x2F;&#x2F;tokio.rs&#x2F;" rel="nofollow">https:&#x2F;&#x2F;tokio.rs&#x2F;</a> and everbody who even looked into network services with rust, stumbled across it.<p>Well maybe for his goals and contributor base go is prefered and that is ok, but well this article is more or less written as a rant against rust, that he&#x2F;she&#x2F;it does not agree with the generel design&#x2F;documentation&#x2F;whatever of rust.<p>In fact I also think that the tooling of rust sucks. rust is a language which shines with extremly good tooling. I mean rust has a godlike package manager and every tooling gets better and better.<p>Compared to go where the package management just sucks but the tooling even IDE completion is extremly great.<p>P.S.: I would not want to have a garbage collected ntp server. But for a lot of things I thing Go would be a good fit, even when it would not be my tool of choice.