The many meaning of Inversion of Control
summary
Explains that dependency injection is one reification of inversion of control and specifically solves four pain points: instance creation, resolving nested dependencies, lazy instantiation and shared instances; contrasts it with service locator which makes the class actively pull from a container. Shows Redux’s four APIs (dispatch, getState, subscribe, replace) to illustrate push vs pull, notes RxJS exposes >100 operators, and argues React’s virtual DOM diffs at runtime while Svelte compiles away the virtual DOM for faster runtime at the cost of tooling/TypeScript support and harder debugging.
AI-written summary · about
chapters (6)
related talks
21mThe many meanings of Inversion of Control (IoC) in JavaScript
34mFlip the Script: Mastering Dependency Inversion in JS/TS Mobile Apps
52mFrom Dependency injection to dependency rejection.
15mRedux is dead, long live redux!
32mWhy Invent a Framework and How to Live with It?
33mDI: DIY
19mMy unpopular ReactJS opinions
25mRedux is dead, long live Redux!