Post

I may or may not be building yet another DI system for Ruby.

This is heavily inspired by Dry::System, but with some features that I wanted for my apps: * An app declares the components it needs, separate from their implementation. * Component implementations can declare their dependencies statically (you can inspect the dependency tree without running)

28/9/26, 12:33 pm0 reposts0 likes

Ismael Celis

@ismaelcelis.com

You can use it for simple config values, but also components that have a lifecycle, such as workers that run in threads or fibers (you can do this with Dry::Types too, I think)