4 ms·

Who is that an issue for? We make simple websites lol.

• black_puppydog 5y ago
  So you mean a piece of code that is literally hanging on the open net, bare-assed? Yeah, I wonder why memory safety would matter here ;)
  • outlawBand 5y ago
    It's up to the user to secure their own memory
  • runawaybottle 5y ago
    Memory allocation and garbage collection is a very solved problem unless you are doing highly performant work. We make websites and mobile apps. Get it?
    • db48x 5y ago
      Yes, there is definitely a trade–off between speed of development and speed of the resulting program. Rust isn’t right for everyone, especially when speed of development is the prime consideration. Even a mediocre server can handle many thousands of requests per second if the software is efficient, but there are plenty of worthwhile projects out there that don’t see that level of usage. For them, garbage –collected languages are perfect.
      • runawaybottle 5y ago
        But what is it that I am fighting against here? Why is my tone a certain way? These people are literally trying to build websites in Rust. Acolytes, cultists.
        • db48x 5y ago
          What’s wrong with that? Rust is great for writing websites. People may choose to make different tradeoffs than you.