Unity VS DryIoc

What I would say about this is that it rarely happens successfully. The reality is that usually no one outside the main maintainers of an OSS project can be bothered / is capable of continuing the project. I often see massive OSS projects run by 1 to a few people, when they want to move on and ask the community to take over there is crickets. A recent example I've seen is the Unity dependency injector. So many people were using it and just 0 real interest in someone actually taking it over.

Autofac is mentioned here https://github.com/unitycontainer/unity/discussions/368

I'd like to keep the convention-based assembly scanning capabilities if ever that was possible. It's too convenient and less error prone than manually registering everything through attributes like current source generator strategies go. DryIocZero supports this somewhat using t4 templates, it gives you a method where you can register your stuff and do assembly scanning and it'll generate your container from there. It works and is quite small and fast but the UX does need some work since t4 is rather clunky to write on.