When would you (not) recommend Go over Rust?

This page summarizes the projects mentioned and recommended in the original post on /r/golang

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • Servo

    Servo, the embeddable, independent, memory-safe, modular, parallel web rendering engine

  • Rust hits a nice sweet spot by allowing you to write almost any multithreading pattern you may need, but statically ensuring that you don't break any of the multithreading rules, and it would be my choice for such a large task. The tradeoff here is that the language itself is more complicated; it's hard to imagine how Rust could run in the 1990s, because even if you teleported the entire source code back in time the computers would be essentially incapable of running it. But this safety does mean you can build complicated multithreaded systems like Servo without it becoming a nightmare. I think that Servo may well be impossible in any other language. I certainly wouldn't dream of taking it on with Go.

  • TinyGo

    Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.

  • Have you seen TinyGo? In the case of embedded system I would probably still chose C over Rust if the system didn't support dynamic memory allocation, and most embedded systems do not.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts