<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>gregwebs</author><text>Send + Sync are great. The downside of concurrency in Rust is:&lt;p&gt;1) There isn&amp;#x27;t transparent integration with IO in the runtime as in Go or Haskell. Rust probably won&amp;#x27;t ever do this because although such a model scales well in general, it does create overhead and a runtime.&lt;p&gt;2) OS threads are difficult to work with compared to a nice M:N threading abstraction (which again are the default in Go or Haskell). OS threads leads to lowest common denominator APIs (there is no way to kill a thread in Rust) and some difficulty in reasoning about performance implications. I am attempting to solve this aspect by using the mioco library, although due to point #1 IO is going to be a little awkward.</text><parent_chain></parent_chain></comment><story><title>Concurrency in Rust</title><url>http://doc.rust-lang.org/book/concurrency.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>nindalf</author><text>I think Steve Klabnik could clarify this, but the book at that link is in the process of being rewritten. I think it might be good to wait until it is. I personally found it slightly difficult to follow compared to other options like the soon to be published Programming Rust.</text><parent_chain></parent_chain></comment><story><title>Concurrency in Rust</title><url>http://doc.rust-lang.org/book/concurrency.html</url></story>