ldlework

Unironically, yes. That's exactly how anarcho-capitalists see it. To them, Anarchy just means "no coercion/state", it doesn't mean a lack of structure, delegation or coordination.

This is quite cool.

Created this short visual narrative with Dall-E in the style of H.R. Giger.

Human figures live their lives in a surreal dystopian world, until they find a hole leading to an even stranger one.

Video was made with React Remotion which was pretty cool. If anything, check that out.

All you've done is push the burden of constructing the dependency to whomever is calling an passing that dependency to __init__

Consistently applied, all construction gets pushed to the entry-point of the program. Congratulations, you've just discovered the so-called "composition root".

Now that all construction is taking place at once, the order matters as you can't pass a dependency to its dependent until the dependency has been constructed. But it may have its own dependencies. So now there is a topological sorting problem.

Turns out computers are really good at topological sorting. So, someone made the computer do it, and we call that a dependency injection container. Tada.

When this was first being presented at the Hackathon where it was created, I joined a few seconds late due to some camera trouble. My first thoughts where "Wow, they really went above and beyond, so tightly choreographing their presentation to their slides." Then it slowly dawned on me what was happening. Funny stuff.

I'm still having this issue.

If the code is implementing against interfaces, why would late binding mess up your IDE experience at all?

In my opinion, you probably don't have good reasons.

> I have a hard time seeing anything new here. > Just .. [a] new perspective...

okie dokie

ITM