<story><title>24 days of Rust – Rayon</title><url>https://siciarz.net/24-days-rust-rayon/</url></story><parent_chain><item><author>StevePerkins</author><text>Are there really a lot of &amp;quot;shared use cases&amp;quot; between Rust and Go?&lt;p&gt;I realize that Go&amp;#x27;s creators intended for it to be a systems language.  In practice though, it has found its niche in web apps or microservices, and command-line apps in the DevOps world.  Rust is primarily aimed toward real-time applications that can&amp;#x27;t tolerate garbage collection latency.&lt;p&gt;Of course they&amp;#x27;re both general-purpose languages in theory.  But in the real world, one is really competing with Java and Python while the other is competing with C++.  I don&amp;#x27;t even see Go and Rust as head-to-head competitors at all... and I definitely don&amp;#x27;t understand their uni-directional &amp;quot;feud&amp;quot; (i.e. nearly every Rust thread is has people taking shots at Go, yet most Go threads don&amp;#x27;t mention Rust at all).</text></item><item><author>lukaslalinsky</author><text>I have not done any real programming in Rust, but whenever I see Rust code I&amp;#x27;m amazed how different is it from Go, despite both having some shared use cases. Go&amp;#x27;s main selling point beyond concurrency is simplicity. And it&amp;#x27;s the simplicity that I like about it. On the other hand, it looks to me like Rust is turning into Scala.</text></item></parent_chain><comment><author>kazagistar</author><text>It&amp;#x27;s a unidirectional feud because Rust isn&amp;#x27;t limiting itself to C++ use cases. As the Async and other library infrastructure falls into place, why not use Rust for webapps, microservices, and command line tools? Just because it is suited for 0-overhead, high safety, with high level abstractions does not mean it&amp;#x27;s unsuited for these other things; or at least we don&amp;#x27;t know yet exactly.&lt;p&gt;On the other hand, Go is aware of its limitations, and thus has no need to fire any shots back, so to speak.</text></comment>
<story><title>24 days of Rust – Rayon</title><url>https://siciarz.net/24-days-rust-rayon/</url></story><parent_chain><item><author>StevePerkins</author><text>Are there really a lot of &amp;quot;shared use cases&amp;quot; between Rust and Go?&lt;p&gt;I realize that Go&amp;#x27;s creators intended for it to be a systems language.  In practice though, it has found its niche in web apps or microservices, and command-line apps in the DevOps world.  Rust is primarily aimed toward real-time applications that can&amp;#x27;t tolerate garbage collection latency.&lt;p&gt;Of course they&amp;#x27;re both general-purpose languages in theory.  But in the real world, one is really competing with Java and Python while the other is competing with C++.  I don&amp;#x27;t even see Go and Rust as head-to-head competitors at all... and I definitely don&amp;#x27;t understand their uni-directional &amp;quot;feud&amp;quot; (i.e. nearly every Rust thread is has people taking shots at Go, yet most Go threads don&amp;#x27;t mention Rust at all).</text></item><item><author>lukaslalinsky</author><text>I have not done any real programming in Rust, but whenever I see Rust code I&amp;#x27;m amazed how different is it from Go, despite both having some shared use cases. Go&amp;#x27;s main selling point beyond concurrency is simplicity. And it&amp;#x27;s the simplicity that I like about it. On the other hand, it looks to me like Rust is turning into Scala.</text></item></parent_chain><comment><author>dispose13432</author><text>&amp;gt;Rust is primarily aimed toward real-time applications that can&amp;#x27;t tolerate garbage collection latency.&lt;p&gt;Why can&amp;#x27;t Firefox tolerate garbage collection latency?</text></comment>