In Go you can immediately tell what the fields are in a config yaml file just by looking at struct annotations. Try doing that with Rust's Serde. Super opaque in my opinion.
In Go you can immediately tell what the fields are in a config yaml file just by looking at struct annotations. Try doing that with Rust's Serde. Super opaque in my opinion.
Rust will only protect me from things my customers don't care about and don't understand.
By not using Rust and just dealing with it, I'm making more money faster than if I started with Rust.
Rust only matters in environments where that calculus comes out the other way.
If your customers are running your software you might have a business model problem instead of a software quality one.
That's the wrong kind of protection. Rust should protect you from things people other than your customers (who presumably are well behaved) care about.
Are you suggesting your customers don't care about CVE's, even indirectly when it affects them?