<story><title>Golang’s most important feature is invisible</title><url>https://blog.devgenius.io/golangs-most-important-feature-is-invisible-6be9c1e7249b?gi=21e47786496b</url></story><parent_chain></parent_chain><comment><author>ricardobeat</author><text>Which part of the example go code looks synchronous? It’s using a callback function. That’s a hallmark of async code, nothing invisible.&lt;p&gt;I also can’t quite grasp the comparison with Java. It’s passing a class instance to the server handler, and that could be doing &lt;i&gt;anything&lt;/i&gt;. Nothing there tells you how async or not the server implementation is, and that `os.write()` call might be using a thread pool underneath.</text></comment>
<story><title>Golang’s most important feature is invisible</title><url>https://blog.devgenius.io/golangs-most-important-feature-is-invisible-6be9c1e7249b?gi=21e47786496b</url></story><parent_chain></parent_chain><comment><author>travisd</author><text>My impression of the article is just that the author is a fan of green threads (goroutines). Green threads don’t really make sense without an integration into some kind of IO runtime, so calling out how Go &lt;i&gt;does&lt;/i&gt; do this seems moot. Other languages with green threads also with this way (Julia comes to mind).</text></comment>