Comment by PeterWhittaker
18 hours ago
This is less a problem with C and more a bad design decision by the musl team. In response to poor practices (programmers not checking what crypt returned), they built an arguably worse one (returning a sentinel value).
Sure, Rust's std::result can make it harder to dumb, but dumb can always find a way.
From the post:
> You can very well write a Rust function that returns "*" if the password is too long. But the big difference between C and Rust in this regard is that the norms of the Rust community do not allow that.
Yeah, read that, laughed. While the statement may have some truthiness, if one flips it around it is basically saying that the norms of musl community allow programmers to be extra dumb.
Taking a different perspective, there are two intertwined thoughts in the original article and in most comments: 1) language safety, 2) community safety.
Each needs to assessed on its own.
People in glass houses: https://github.com/nextest-rs/nextest/security/advisories/GH...
Whataboutery generally makes it quite clear that your arguments are not in good faith.
2 replies →