butterknife VS Guice

Oof, Infinity uses the long deprecated butterknife, and I'm unable to compile on my m1. Fave part of programming: getting things to run the first time.

Usually each context has a different scope and lifetime associated with it. Here, it sounds like there are two distinct scopes: server and request (cf. how Guice models scopes: https://github.com/google/guice/wiki/Scopes). It is rarely sensible to merge the scopes or contexts together. If we think about a context, it contains several things:

using libraries from java world, such as Guice;

As said in the title, we will focus on the dependency inversion principle and one of its application : dependency injection. For production-ready applications, it would be better to rely on a framework and not implement its own container. For it, the java ecosystem have 3 frameworks available : Spring, Guice and Dagger.

And it doesn't really matter whether you have created circular reference structure of whether you have messed up your binding and now objects which was supposed to disappear after one request is only doing that when all database connections are quiescent (which happens easily in testing, but may not happen for days in production).

https://github.com/google/guice/issues/1536

... with guice or Spring Boot,

The following section is an example of injecting our service using Guice, a dependency injection framework for Java made by Google. The concept is to reference bindings of every component you can inject in your program, so that the library can generate a class of any type, automatically.

But of course there are good Java examples, too! One of them is Guice: