<story><title>Clojure core.async and Go: A Code Comparison</title><url>http://blog.drewolson.org/blog/2013/07/04/clojure-core-dot-async-and-go-a-code-comparison/</url></story><parent_chain></parent_chain><comment><author>nickik</author><text>This is very cool and intressting. I have to think about something to do with core.async.&lt;p&gt;This is also a good example why macros are just awesome. Go is a language design to work well with goroutins and channels, but the clojure code looks just as good and readable. You could simply not have such idiomatic use of these concepts without macros.&lt;p&gt;Or am I wrong, can a flexible language like scala or python be extended to look as good for that usecase? I dont know enougth of the tricks scala people use, I cant juge if it is possible.</text></comment>
<story><title>Clojure core.async and Go: A Code Comparison</title><url>http://blog.drewolson.org/blog/2013/07/04/clojure-core-dot-async-and-go-a-code-comparison/</url></story><parent_chain></parent_chain><comment><author>hueyp</author><text>Are the clojure threads actually lightweight?  Thread&amp;#x2F;sleep is blocking so you&amp;#x27;d need to occupy 10 threads right?  If you wanted to sleep without blocking a real thread would you use an executor service to write to a channel after delay and block on that?</text></comment>