<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>FlyingSnake</author><text>Agreed.&lt;p&gt;Rust is like a fresh breath of air, and the community around the language is a great example how an OpenSource project can work without being hostile to newcomers. Kudos to the Rust team!</text><parent_chain><item><author>brandur</author><text>I&amp;#x27;m consistently blown away by just how good the project management for this language is. It&amp;#x27;s not just the forward progress that the language is making (which is considerable), but also just how well they package the information up into a form that the rest of us who are not involved day to day can digest, like has been done here.&lt;p&gt;Another example is the &amp;quot;This Week in Rust&amp;quot; newsletter which takes progress that would&amp;#x27;ve taken you hours to read about yourself, and puts it into a succinct format that you can get through in minutes [1].&lt;p&gt;The Rust 2017 roadmap which targeted forward movement on all the language&amp;#x27;s weakest features was admirable in itself, but even moreso is how much progress has already been made. In particular, I&amp;#x27;m really excited about incremental compilation, which is showing as much as 5x speedups in early results [2].&lt;p&gt;I was also very happy to hear that the Rust team acknowledges that regardless of how performant they are, futures are &lt;i&gt;not&lt;/i&gt; a particularly ergonomic or maintainable way to write code, and are considering what new constructs might look like over the longer term:&lt;p&gt;&amp;gt; &lt;i&gt;Over the rest of this year, we expect all of the above libraries to significantly mature; for a middleware ecosystem to sprout up; for the selection of supported protocols and services to grow; and, quite possibly, to tie all this all together with an async&amp;#x2F;await notation that works natively with Rust’s futures.&lt;/i&gt;&lt;p&gt;I&amp;#x27;m still on dabbling in Rust, but I&amp;#x27;m fairly convinced that in another few years after this Tokio churn has gotten a chance to settle down and the async patterns are more broadly refined, there won&amp;#x27;t be many justifiable reasons to &lt;i&gt;not&lt;/i&gt; write new projects in it, whether they&amp;#x27;re as low level as a Postgres extension, or as high level as a DB-backed HTTP application. It seems to have an almost perfect compromise between performance, safety, productivity, and ecosystem.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;this-week-in-rust.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;this-week-in-rust.org&amp;#x2F;&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.rust-lang.org&amp;#x2F;2017&amp;#x2F;05&amp;#x2F;15&amp;#x2F;rust-at-two-years.html#rust-should-have-a-pleasant-edit-compile-debug-cycle&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.rust-lang.org&amp;#x2F;2017&amp;#x2F;05&amp;#x2F;15&amp;#x2F;rust-at-two-years.html...&lt;/a&gt;</text></item></parent_chain></comment><story><title>Two years of Rust</title><url>https://blog.rust-lang.org/2017/05/15/rust-at-two-years.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>sillysaurus3</author><text>&lt;i&gt;I&amp;#x27;m still on dabbling in Rust, but I&amp;#x27;m fairly convinced that in another few years after this Tokio churn has gotten a chance to settle down and the async patterns are more broadly refined, there won&amp;#x27;t be many justifiable reasons to not write new projects in it, whether they&amp;#x27;re as low level as a Postgres extension or as high level as a DB-backed HTTP application.&lt;/i&gt;&lt;p&gt;Not being hindered by the compiler telling you what you can and can&amp;#x27;t do; freeing yourself from the write-compile-debug cycle, reducing it to repl-done; etc.</text><parent_chain><item><author>brandur</author><text>I&amp;#x27;m consistently blown away by just how good the project management for this language is. It&amp;#x27;s not just the forward progress that the language is making (which is considerable), but also just how well they package the information up into a form that the rest of us who are not involved day to day can digest, like has been done here.&lt;p&gt;Another example is the &amp;quot;This Week in Rust&amp;quot; newsletter which takes progress that would&amp;#x27;ve taken you hours to read about yourself, and puts it into a succinct format that you can get through in minutes [1].&lt;p&gt;The Rust 2017 roadmap which targeted forward movement on all the language&amp;#x27;s weakest features was admirable in itself, but even moreso is how much progress has already been made. In particular, I&amp;#x27;m really excited about incremental compilation, which is showing as much as 5x speedups in early results [2].&lt;p&gt;I was also very happy to hear that the Rust team acknowledges that regardless of how performant they are, futures are &lt;i&gt;not&lt;/i&gt; a particularly ergonomic or maintainable way to write code, and are considering what new constructs might look like over the longer term:&lt;p&gt;&amp;gt; &lt;i&gt;Over the rest of this year, we expect all of the above libraries to significantly mature; for a middleware ecosystem to sprout up; for the selection of supported protocols and services to grow; and, quite possibly, to tie all this all together with an async&amp;#x2F;await notation that works natively with Rust’s futures.&lt;/i&gt;&lt;p&gt;I&amp;#x27;m still on dabbling in Rust, but I&amp;#x27;m fairly convinced that in another few years after this Tokio churn has gotten a chance to settle down and the async patterns are more broadly refined, there won&amp;#x27;t be many justifiable reasons to &lt;i&gt;not&lt;/i&gt; write new projects in it, whether they&amp;#x27;re as low level as a Postgres extension, or as high level as a DB-backed HTTP application. It seems to have an almost perfect compromise between performance, safety, productivity, and ecosystem.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;this-week-in-rust.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;this-week-in-rust.org&amp;#x2F;&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.rust-lang.org&amp;#x2F;2017&amp;#x2F;05&amp;#x2F;15&amp;#x2F;rust-at-two-years.html#rust-should-have-a-pleasant-edit-compile-debug-cycle&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.rust-lang.org&amp;#x2F;2017&amp;#x2F;05&amp;#x2F;15&amp;#x2F;rust-at-two-years.html...&lt;/a&gt;</text></item></parent_chain></comment><story><title>Two years of Rust</title><url>https://blog.rust-lang.org/2017/05/15/rust-at-two-years.html</url></story>