> I wish there was some process to cannibalize the most useful crates.
There is, and this is exactly what has been happening. Early crates showed some of the weaknesses in the Error trait, and then they were addressed. Failure was created, showed more holes, and they were addressed. Now anyhow/thiserr/other stuff have happened, and their improvements may or may not make it upstream.
> Also is it even possible to standardize error handling best practices across entirely different software components like an OS kernel, a web service and a CLI tool?
Some of the details differ, but it feels like we're at that point to me.
> OS kernel should not panic? Service absolutely should panic ...
Both of these are specific implementation choices, and some people will choose different options for each of them. It just really depends. But with Result (and to some extent, the Error trait), there are means to share the bits that make sense. The core of it is broadly applicable even if some of the details change.