This has come up several times in the past. One name for it was stdx. Some in the ecosystem are very cautious of picking winners and losers, limiting the expo

This has come up several times in the past. One name for it was stdx. Some in the ecosystem are very cautious of picking winners and losers, limiting the exposure to new break-out crates. Rarely recommending crates for different problems. This comes at the cost of making it a harder barrier to get involved because you need to be "in the know" for what crates to use or avoid. Another problem with stdx is if anyone uses types from this in their public API, they are decoupled from the individual crates semver constraints which makes it hard to know which breaking changes from your dependency are a breaking change in your API.