Three degrees of inversion of control.

Inversion of control is a paradigm by Martin Fowler that advocates for separating things that don't belong together during object creation.

What exactly should be split from what? Different frameworks answer the question slightly differently. They do at least 1 of these three:

1. Eliminate direct constructor calls. All dependency injection frameworks do that.
   
2. Strictly separate business logic from object creation. Google Guice, among others, allows that, but doesn't enforce that.
   
3. Eliminate all static references. Newspeak makes all lookups dynamic, thereby eliminating global state.
   

All three are compatible with one another. Can they be combined in practice? I'm working on it …