<story><title>Rust for Web</title><url>https://medium.com/@eugeniyoz/restful-api-in-rust-impressions-63250d611d15</url></story><parent_chain><item><author>kibwen</author><text>I&amp;#x27;m continually delighted to see so many programmers with backgrounds in dynamic languages feeling at home in Rust, given that that&amp;#x27;s my trajectory as well. :) I&amp;#x27;m giving a three-hour Rust tutorial at OSCON this year and I&amp;#x27;m honestly torn over whether I should tailor it towards people coming from dynamic langs or people coming from C&amp;#x2F;C++. I feel like I might end up just having to write two tutorials and take a survey as people come in to determine which to focus on.</text></item></parent_chain><comment><author>StevePerkins</author><text>The creators of Go assumed that their primary audience would be disgruntled C++ devs, and were surprised to find instead that it&amp;#x27;s mostly Ruby and Node.js people.&lt;p&gt;Despite all of the &amp;quot;systems language&amp;quot; talk, it would not shock me in the least to see the same thing happen with Rust (or whatever new language comes along next year).&lt;p&gt;I don&amp;#x27;t intend for this to be a slight, but the plain fact of the matter is that &amp;quot;dynamic&amp;quot; languages come in and out of fashion every 5 years or so.  Those people are accustomed to that cycle.  They get bored easily and PREFER that cycle.  The senior ones are usually on their second or third language cycle (or beyond).&lt;p&gt;In contrast, C++ and Java are ENTRENCHED in their areas (systems programming and business applications, respectively).  Whatever ultimately displaces them someday... it will have to be an order of magnitude better, and it would still take years.&lt;p&gt;By all means, market your favorite new language(s) to all possible demographics.  Just understand that the &amp;quot;PHP&amp;#x2F;Python&amp;#x2F;Ruby&amp;#x2F;Node&amp;#x2F;Go&amp;#x2F;Elixir&amp;#x2F;Swift&amp;quot; crowd are going to be your primary adopters (and conversely, the first to grow bored and leave when the next thing comes along).</text></comment>
<story><title>Rust for Web</title><url>https://medium.com/@eugeniyoz/restful-api-in-rust-impressions-63250d611d15</url></story><parent_chain><item><author>kibwen</author><text>I&amp;#x27;m continually delighted to see so many programmers with backgrounds in dynamic languages feeling at home in Rust, given that that&amp;#x27;s my trajectory as well. :) I&amp;#x27;m giving a three-hour Rust tutorial at OSCON this year and I&amp;#x27;m honestly torn over whether I should tailor it towards people coming from dynamic langs or people coming from C&amp;#x2F;C++. I feel like I might end up just having to write two tutorials and take a survey as people come in to determine which to focus on.</text></item></parent_chain><comment><author>dikaiosune</author><text>Not sure whether this is relevant for your talk, but I rarely see these introductory talks address a language that a lot of people write and which intended to provide several of the same guarantees that Rust does: Java. Java has statically typed &amp;quot;safety&amp;quot; (which is something most Rust talks pitch to dynamic lang devs), decent performance approaching C&amp;#x2F;C++ for long-running tasks, etc.&lt;p&gt;I think Rust does &lt;i&gt;way&lt;/i&gt; better at most of Java&amp;#x27;s strong and weak points (aside from maybe ecosystem and current deployments), but it would be good at some point for Rust to have a good story to present to Java devs. Its type system is much better, its safety guarantees stronger, it has pretty good cache locality, its concurrency is approaching the ease of use of the JVM&amp;#x27;s and has always been safer, and its use of memory is far more reasonable and isn&amp;#x27;t prone to GC pause.</text></comment>