

I think the issue with Rust and unsafe is that people can't really handle and don't really want ambiguous shades of grey. I comment on Reddit sometimes and I roll my eyes every time I’ve done it lately.

I’ll take slightly better with crazy good performance over not better at all with no guarantees.Īlso, look, the other problem is Reddit: I’m starting to think larger projects should squat their name there and redirect to better discussion places. I know it kind of explains this already, but perhaps being more blunt?Īctix-web even with a few unsafe is still more sound than most frameworks IMO. I have to wonder if the Rust docs couldn’t better point out “the goal is less unsafes, but unsafes will exist - this is fine”. It often feels like newcomers and zealots preaching the unsafe issue, too.

You’re not replacing decades of computing overnight, though, and it’s not the end of the world if it’s there sometimes. Setting aside actix-web, the community has this really annoying obsession with not using unsafe anywhere. Unsafe isn’t something you live without, you just avoid unless there’s a decent reason.
#Sales force actix pricing code
It's unfortunate that the maintainer has stepped down entirely instead of changing how they are interacting with the community, but purely from a security standpoint I would rather a slower (but more secure and receptive) library take it's place than have a very popular library maintained by someone who doesn't seem to care about the overall code quality of the library they are a steward of. Our entire ecosystem that we have built (for better or for worse) by using these libraries as the foundations for countless projects necessitates that when a community is willing to give their time to improve a library that you maintain, the minimum that is to be expected is that you treat sincere contributions respectfully and not dismiss them out of hand. But at the same time I really think almost all of the blame in this case rests solely with the reception (or lack thereof entirely) of PRs/issues that are intending to improve the quality of a library that many people have come to rely on. I can see where Steve is coming from about the difficulties of maintainer-ship - I only have a few projects that I am actively maintaining and obviously nothing close to the scale of a popular library.
