News for hackers. Stuff that matters.
Re:Clojure Concurrency Tutorial by Blackthorn on Tuesday April 09, 2019 @01:43PM (#19617174)
core.async is a macro. Call an already compiled function under a library that blocks and the whole system will come to a screeching halt. Goroutines don't have that limitation.
Re:Clojure Concurrency Tutorial by jwr on Wednesday April 10, 2019 @01:12AM (#19622041)
Please see my other comment about using the same channels and calling I/O-heavy (blocking) functions from a `(thread)` instead of from a go block. You indeed shouldn't call blocking functions from go blocks, but core.async gives you the option of freely mixing separate threads and go blocks.
Re:Clojure Concurrency Tutorial by Blackthorn on Wednesday April 10, 2019 @09:49AM (#19624560)
Having to use full threads in some cases and core.async in others pretty much defeats the purpose. Core.async is just nowhere near as good as goroutines. It'll continue to be like that until Project Loom finally has a release.
Re:Clojure Concurrency Tutorial by jwr on Tuesday April 16, 2019 @11:52AM (#19674708)
I think you misunderstood what I wrote.

Core.async lets you freely mix both. You use the same channels, the only difference being that your coroutine blocks will be wrapped in `go` and use `<!` (parks coroutine if it needs to block), while your full threads with be wrapped in `thread` and use `<!!` (blocks). It makes the tradeoffs explicit (the tradeoff always exists) and isn't a problem at all.

Re:Clojure Concurrency Tutorial by tombert on Wednesday April 10, 2019 @11:00AM (#19625358)
Sorry, what is Project Loom? I'm not overly familiar with it and a quick search for `clojure project loom` seems to indicate that it's a graphing library.
Re:Clojure Concurrency Tutorial by lackbeard on Wednesday April 10, 2019 @02:49PM (#19627640)