6 ms·
I'm betting that hiring is harder for Rust. The post gives Go 3/5 for stability, and Rust gets 5/5 for it's memory safety benefits. The post says that memory s
by Comevius 4y ago
I'm betting that hiring is harder for Rust.
The post gives Go 3/5 for stability, and Rust gets 5/5 for it's memory safety benefits. The post says that memory safety was the primary deciding factor. Hello? Go and Node.js are garbage collected. They are trivially memory safe. Rust's borrow checker is helpful, but it does not make memory safety trivial.
The post concludes that Rust attracts more transgender people than other communities. Even if that's true, how is that going to help the business? It's not like they should be hiring based on gender.
Although Rust + Electron works, Dart + Flutter would trivially beat this particular combination in developer convenience and productivity, and also user experience.
- tronono 4y ago
- deleted 4y ago[deleted]
- 3836293648 4y agoYou missed the point about leaks. It's not a part of Rust's usual pitch, but they mention it here as a major point, given how they're a background service that can run for months on end
- Comevius 4y agoRust gives you freedom in designing a perfect long-running service, but if you are not doing it from scratch you will be relying on an async runtime like Tokio. Go's flawed memory model nonwithstanding this use case is simple enough to be able to avoid or recover from races and leaks with less work. When concurrency is important and you are not designing lock-free algorithms I would sooner go with Erlang or Elixir than Rust. If you are designing concurrent algorithms with liveness guarantees you are in the TLA+, fighting the C11 memory model, unsafe Rust territory.