<story><title>Rust at OneSignal</title><url>https://onesignal.com/blog/rust-at-onesignal/</url></story><parent_chain></parent_chain><comment><author>chamakits</author><text>First, I have to comment on that diagram:&lt;p&gt;That diagram is the most interesting representation of a diagram I have ever seen.  Do you have a tool to generate these for you, or was it hand crafted for this post?  If it&amp;#x27;s a tool, is it available anywhere? If this is a built out tool, I would use this tool all the time.&lt;p&gt;On the article itself:&lt;p&gt;This is the most interesting type of posts about choosing Rust.  Very balanced and aware that Rust gives a lot of upsides, but compared to other alternatives there are measurable downsides as well.&lt;p&gt;I think the biggest trade-off that they identified (and I&amp;#x27;ve also gotten the impression from writing Rust on my own time, not for work) is the relative immaturity of the ecosystem, in as far as libraries available, and amount of developers supporting some of these libraries.  What makes me hopeful, is that as a stable language (post 1.0) Rust is still relatively young.  And you can definitely see things improving, with the community growing, more libraries propping up, and also gathering around specific libraries.</text></comment>
<story><title>Rust at OneSignal</title><url>https://onesignal.com/blog/rust-at-onesignal/</url></story><parent_chain></parent_chain><comment><author>staticassertion</author><text>This is an excellent blog post - thanks a lot for writing it up. Solid use cases defined, I particularly enjoyed how you dealt with the shortcomings of joining a relatively young language.&lt;p&gt;The &amp;#x27;belligerent refactoring&amp;#x27; resonated with me - I have worked on untyped and statically typed codebases of varying sizes and when making huge changes there is no better tool for me personally than an expressive type system.</text></comment>