That's trivially true. But a web backend will preferably use: - A std library that provides much of the stuff you need to write web servers. - A few select we

That's trivially true. But a web backend will preferably use: - A std library that provides much of the stuff you need to write web servers. - A few select well established, stable libraries to fill the gaps - A battle hardened database like SQLite, MySQL or Postgres - Maybe additional libraries and generators to program against specific, open protocols, standards and over the wire schemas, like json-schema/OpenAPI/GraphQL/Protobuf etc. Which are typically tested against a common test-suite. - Maybe additional components like message queues and key value stores and object storage in order to scale. You get the drift. It's not like these things are some random libs and tools that are maybe "unsafe" (whatever that means). A good thing about Rust is that unsafe is always explicit. And if you're not using the keyword, then satisfying the type checker gives a "if it compiles, it runs" feel, because runtime assertions can be avoided. But saying "anything is unsafe anyways" is missing the point. The language itself can nudge you towards a certain outcome, but I trust some of the mentioned technologies above, not because of the languages they use, but because they are well designed, stable and full of old battle scars.