ManualDi.Unity3d VS di-framework

Hello everyone! I love unity, it is a great game engine, but I always find myself back to the same architectural hurdles again and again. I used Zenject for several small projects, but I didn't completely like the approach it imposes. In order to improve on what I felt Zenject lacked, decided to make a dependency injection container that fit what I felt was necessary. https://github.com/PereViader/ManualDi.Main (core of the container, just c#) https://github.com/PereViader/ManualDi.Unity3d (extensions to improve usage in unity) As far as I know, dependency injection containers are not a very hot topic around the game dev sphere. Something I think is really not ideal for engineers, as I believe it greatly improves our productivity. What do you think of dependency injection in Unity? What do you think a dependency injection container should have for you to use them in your projects?

For the past few month I've been developing a dependency injection solution for Unity in order to overcome difficulties I had while working even with medium-sized projects. That is, over time, it becomes really annoying to assign dependencies in Inspector/bloat Awake methods with GetComponent and similar calls. The framework is available at GitHub as a package for Unity: https://github.com/Delt06/di-framework. Any feedback is welcome!