Why Rust is a great choice for startups
I started my first Rust project a month ago after working for years in Golang and before that Python (and before that Perl, C&#x2F;C++ and Turbo Pascal). I really like the whole experience but I&#x27;m not sure if I&#x27;d recommend writing all your backend code in Rust as a startup.<p>Rust definitely provides a pleasant experience and is very powerful. If you can stick to the standard library I think Rust is great, though the package ecosystem is still lacking in many respects and most packages seem immature and quite limited. So if you plan to build something that has sizeable external dependencies plan some time to either write that yourself or to spend a lot of time debugging and vetting external packages, many of which are maintained as side projects by single developers. Documentation often also seems to be subpar as compared to e.g. Python. I suppose that&#x27;s due to the auto-generation of documentation which seems to lead to people mostly writing what I&#x27;d refer to as API documentation with very few tutorials.<p>So is Rust worth it for a startup? Not so sure. I recently picked up Python again to write a simple REST API, and the process is just so much faster and (for me) enjoyable because of the &quot;ad hocness&quot; of the language and of course the great existing tooling around it (I still have to find an ORM as powerful as SQLAlchemy in Rust or Golang). And let&#x27;s be honest it&#x27;s also possible to write great scalable services in Python (or Ruby, or Javascript), as many scaleups still use these technologies.<p>Onboarding of developers might be another issue: Yeah, everyone wants to be a Rust programmer, but for people that have little experience with systems programming the learning curve is quite steep, so you&#x27;ll limit your candidate pool quite a bit and will need more time for hiring.