It depends on what your goals are. If you pick Rust for your product be ready to roll up your sleeves and contribute to the crates you are depending on. IMO your investment is worth it because developing in Rust is a delight and when it works it will be very solid, but the ecosystem isn't as mature yet.
If you want to focus on building a product and get something out there relatively quickly, C++ has a huge amount of ready-to-use libraries, but you're on your own with making sure to run sanitizers and making any sense of object lifetime and thread safety. You might ship an MVP faster but I wouldn't want to maintain it after that IMO.
Personally I've made peace with the Rust ecosystem being not-quite-there because I can see that many things are about to get to the point of being really solid. There's a lot of hard-working folks volunteering their time to build out great libraries, and I'm hopeful that the 2024 edition is going to be a huge improvement for async ergonomics.
If you want to focus on building a product and get something out there relatively quickly, C++ has a huge amount of ready-to-use libraries, but you're on your own with making sure to run sanitizers and making any sense of object lifetime and thread safety. You might ship an MVP faster but I wouldn't want to maintain it after that IMO.
Personally I've made peace with the Rust ecosystem being not-quite-there because I can see that many things are about to get to the point of being really solid. There's a lot of hard-working folks volunteering their time to build out great libraries, and I'm hopeful that the 2024 edition is going to be a huge improvement for async ergonomics.