6 ms·

It stays with you until you need to change something and find yourself unable to make incremental changes. And in many use cases people are throwing Rust (and

by jstx1 3y ago

It stays with you until you need to change something and find yourself unable to make incremental changes. And in many use cases people are throwing Rust (and especially async Rust) on problems solved just fine with GC languages so the safety argument doesn’t apply there.

brigadier132 3y ago
> change something and find yourself unable to make incremental changes why do you believe this becomes the case with rust code?
imtringued 3y ago
The safety argument is actually the reason why you can use Rust in those cases to begin with. If it was C or C++ you simply couldn't use it for things like webservers due to the safety problems inherent to these languages. So Rust creeps into the part of the market that used to be exclusive to GC languages.
- maccard 3y ago
  What do you think nginx and Apache are written in?
  - ttfkam 3y ago
    How few severe vulnerabilities and other major defects (memory corruption or crashes) do you think Nginx and Apache have had over the years?
sliken 3y ago
Sort of. Do you want someone that doesn't understand the constraints that likely is creating a bug that will cause crashes? Or do you want to block them until they understand the constraints?