Some questions

[onlyamessenger]

I have a couple of questions regarding this library, I didn't see where else to reach you regarding dryice, so posting an issue.

• How does Dryice compare to something like Google's Dagger under the hood?
• What makes Dryice better than tools like inject.dart developed by a team at Google?
• What are the requirements and or policies for contributing?
• Can I contribute a Flutter example?

Look forward to hearing from you.

[MikeMitterer]

Dagger - I think you can't compare the two. These products are complete different. What makes it better than inject.dart? I had no time to try inject.dart so - no idea. What are the requirements and or policies for contributing. There are no special requirements. Can I contribute a Flutter example - sure, you are more than welcome.

I made DryIce mainly for my m4d_-packages: https://pub.dartlang.org/packages?q=m4d_ and I had the whole thing running with DryIce but ~ 2 month ago I decided to remove the whole DI stuff from all of my libs.

As said it worked but alle those generated files by reflectable cause more problem than they solved.

I'm really a big fan of DI and I used it in all my other projects but the leak of native support in Dart makes it quite problematic. My solution was to write a small IOC-package https://github.com/MikeMitterer/m4d_core/blob/master/lib/m4d_ioc.dart. This thing works better than expected. It's not really type save but in general it does it's job quite well. Everything happens at runtime. No xxx.reflectable.dart files. Testing works nice too.