Rust advocacy at a medium-sized startup
&gt; I didn’t want to talk about Go because it’s simply not what I was passionate about. I also didn’t want to put down Go users in the company. I just wanted to extol the benefits of Rust and see if anyone was interested in trying it out.<p>&gt; Yet, it made me sad to look up articles on the language just to, in effect, bash it. I’m not generally in the business of discouraging people from coding, regardless of what their favorite programming language was.<p>While this level of self reflection shows a lot of maturity, if your judgement is clouded by excitement and you&#x27;re searching for evidence to support your plan, this is _exactly the wrong_ time to attempt to shift your organization&#x27;s direction. You&#x27;re on tilt.<p>Worse, others are likely to recognize that you&#x27;re on tilt, and discount otherwise rational arguments that you&#x27;re making. It won&#x27;t be clear to you why you&#x27;re not making progress.<p>I&#x27;ve introduced Rust to an organization for a specific project, and it wasn&#x27;t a decision taken lightly. It fit the problem domain well. I&#x27;ll likely advocate against Rust for the next greenfield project that&#x27;s on the horizon - as it&#x27;s not nearly as much of a fit.<p>These are tools and there is no silver bullet.<p>This doesn&#x27;t apply (as other commenters have said) to quitting and getting a job elsewhere that already uses Rust. Indulge in your passion without engaging in a sisyphean battle that&#x27;ll burn you out and harm the business.