<story><title>The Adoption of Rust in Business</title><url>https://rustmagazine.org/issue-1/2022-review-the-adoption-of-rust-in-business/</url></story><parent_chain><item><author>bin_bash</author><text>As a counterpoint, I’m a senior engineer at FAANG with 15 professional YOE. I’ve mostly used scripting languages in my career though.&lt;p&gt;It took me probably more like 1-2 months to really understand how to code in Rust. I do not think a typical team of JS&amp;#x2F;Python devs would be productive in 3 weeks. I think it would be more like 3 months. Developers with C++ experience seem to pick it up much quicker.&lt;p&gt;Also, at this point I’m pretty proficient in rust but I’m still far slower than I would be in a scripting language. So I don’t think anyone would ever reach “equally productive” unless they’re comparing themselves to another compiled language.&lt;p&gt;I like Rust, but it’s challenging, and it’s certainly not a language for rapid development.</text></item><item><author>yazaddaruvala</author><text>I feel like it took me 2 weekends to &amp;quot;learn Rust&amp;quot; enough to make feature changes, and another 2 weekends to really &amp;quot;get it&amp;quot; enough to build basic abstractions.&lt;p&gt;I feel like it would take another week or two to learn some of the UnsafeCell&amp;#x2F;Pin&amp;#x2F;Generators type stuff, but none of that is needed for 95%+ of Rust code.&lt;p&gt;I think if you and your team just started learning Rust week by week, you&amp;#x27;d find in 3 weeks that you&amp;#x27;re equally productive in Rust than your current languages. Especially given the code base already exists. Even just starting to learn Rust by writing tests (if there aren&amp;#x27;t) would be sufficient to improve that system rather than wait to hire or re-write it.</text></item><item><author>TrackerFF</author><text>The organization (gov.) I work for recently took over a product where the entire back-end was written in Rust. Basically the product was developed by a bunch of Rust enthusiasts in a R&amp;amp;D group, and the product was wholly financed by gov. grants. When that money dried out, they were faced with either just shutting it down, or trying to sell or give the product away. Some higher-ups decided this could be a great internal tool, and got it for free.&lt;p&gt;The product works great, but the codebase is around 400k LOC of Rust, and we don&amp;#x27;t have any budget to hire Rust developers. And when we had a budget in November, it was really hard to find anyone local (work requires a high security clearance, and remote is not possible for this kind of work due to said security issues).&lt;p&gt;So we&amp;#x27;re kind of stuck with just keeping it around until better times, or just re-writing the entire back-end in something we know better. Not to sound like a downer, just an example of what Rust adaption could look like from the other side.</text></item></parent_chain><comment><author>zozbot234</author><text>&amp;gt; It took me probably more like 1-2 months to really understand how to code in Rust. I do not think a typical team of JS&amp;#x2F;Python devs would be productive in 3 weeks. I think it would be more like 3 months.&lt;p&gt;This is actually a very fast learning curve.  Imagine a typical Python&amp;#x2F;JS developer becoming proficient with real, production-quality C++ in 3 months?  The very notion seems ludicrous to even think about.  So the Rust folks are not wrong when they point out that Rust is about empowering developers and enabling higher quality software across the board.</text></comment>
<story><title>The Adoption of Rust in Business</title><url>https://rustmagazine.org/issue-1/2022-review-the-adoption-of-rust-in-business/</url></story><parent_chain><item><author>bin_bash</author><text>As a counterpoint, I’m a senior engineer at FAANG with 15 professional YOE. I’ve mostly used scripting languages in my career though.&lt;p&gt;It took me probably more like 1-2 months to really understand how to code in Rust. I do not think a typical team of JS&amp;#x2F;Python devs would be productive in 3 weeks. I think it would be more like 3 months. Developers with C++ experience seem to pick it up much quicker.&lt;p&gt;Also, at this point I’m pretty proficient in rust but I’m still far slower than I would be in a scripting language. So I don’t think anyone would ever reach “equally productive” unless they’re comparing themselves to another compiled language.&lt;p&gt;I like Rust, but it’s challenging, and it’s certainly not a language for rapid development.</text></item><item><author>yazaddaruvala</author><text>I feel like it took me 2 weekends to &amp;quot;learn Rust&amp;quot; enough to make feature changes, and another 2 weekends to really &amp;quot;get it&amp;quot; enough to build basic abstractions.&lt;p&gt;I feel like it would take another week or two to learn some of the UnsafeCell&amp;#x2F;Pin&amp;#x2F;Generators type stuff, but none of that is needed for 95%+ of Rust code.&lt;p&gt;I think if you and your team just started learning Rust week by week, you&amp;#x27;d find in 3 weeks that you&amp;#x27;re equally productive in Rust than your current languages. Especially given the code base already exists. Even just starting to learn Rust by writing tests (if there aren&amp;#x27;t) would be sufficient to improve that system rather than wait to hire or re-write it.</text></item><item><author>TrackerFF</author><text>The organization (gov.) I work for recently took over a product where the entire back-end was written in Rust. Basically the product was developed by a bunch of Rust enthusiasts in a R&amp;amp;D group, and the product was wholly financed by gov. grants. When that money dried out, they were faced with either just shutting it down, or trying to sell or give the product away. Some higher-ups decided this could be a great internal tool, and got it for free.&lt;p&gt;The product works great, but the codebase is around 400k LOC of Rust, and we don&amp;#x27;t have any budget to hire Rust developers. And when we had a budget in November, it was really hard to find anyone local (work requires a high security clearance, and remote is not possible for this kind of work due to said security issues).&lt;p&gt;So we&amp;#x27;re kind of stuck with just keeping it around until better times, or just re-writing the entire back-end in something we know better. Not to sound like a downer, just an example of what Rust adaption could look like from the other side.</text></item></parent_chain><comment><author>LoganDark</author><text>&amp;gt; It took me probably more like 1-2 months to really understand how to code in Rust. I do not think a typical team of JS&amp;#x2F;Python devs would be productive in 3 weeks. I think it would be more like 3 months.&lt;p&gt;Our very first Rust project (to learn the language) was a path tracer that was done (fully functional) in 2 weeks. I doubt it would take a team 3 months to become productive in Rust. There&amp;#x27;s always more to learn, but &amp;quot;being productive&amp;quot; is quite a low bar if they already know basic programming concepts.&lt;p&gt;With that said, &amp;quot;typical JS&amp;#x2F;Python devs&amp;quot; might not even know said basic programming concepts, so maybe you&amp;#x27;re talking about those? Regardless, 3 months is an extremely conservative estimate.&lt;p&gt;-Emily</text></comment>