Should C++ be deprecated?
Should C++ be deprecated?
Posted Sep 23, 2025 15:53 UTC (Tue) by farnz (subscriber, #17727)In reply to: Should C++ be deprecated? by marcH
Parent article: Comparing Rust to Carbon
In terms of SBOM constraints and the Rust ecosystem, I see one essential tool, and two things competing for "long term direction".
The essential tool is cargo deny, which gives you three vital features (plus checking SPDX licensing tags):
- You can block known vulnerable or unmaintained dependencies, so that you're not accidentally using something that's definitely bad, or that isn't being looked after.
- You can ban specific dependencies, or certain versions of dependencies, so that you can stop people pulling in multiple libraries for the same task, or ban versions that you know don't work well with your codebase. This can be done as an allowlist of things you're letting in, or a denylist of things you do not want.
- You can check that all dependencies come from a known-good source, rather than letting people point you at a random hosting site. This can also be used to prevent people pointing you at a random repo on a big hosting site like GitLab or BitBucket.
On top of that, you also want some functionality to at least let you distinguish "the code in this dependency has been audited by a trustworthy party" from "we're using this because it works, and we need to audit it before release". cargo vet does that with explicitly configured lists of trusted audits (and no transitive trust), cargo crev does that via a web of trust setup.
I have no particular bias towards either tool; both look like they could be made to work, and which one ends up preferred depends on details of what you're doing and how you determine who to trust.