Frameworks on Artur Rios Lab

What Is Inversion of Control? Frameworks, Callbacks, Dependency Injection and Containers

Tue, 20 Oct 2026 23:00:00 +0000

A web framework calls a function when a request arrives. A test runner finds the tests in a file and runs each one. A browser calls a handler when a button is clicked, and an application server hands a class the database connection it asked for in its constructor. In each case the code a programmer wrote does not decide when it runs or where its collaborators come from: something else does. That reversal has a name, inversion of control, and it is one of the ideas most of modern software is quietly built on. This article explains what it means, where the term came from, the forms it takes, how dependency injection and IoC containers work inside, and when the indirection is worth paying for. It closes a series on SOLID: where the dependency inversion principle says which way dependencies should point, this is the mechanism that makes them point that way at run time. Every output shown here was produced by running the code on Windows 11, with Python 3.14.6 and with the .NET 10 SDK and Microsoft.Extensions.DependencyInjection 10.0.13, not written by hand.

Angular, React or Flutter? How They Compare and How to Choose

Tue, 20 Oct 2026 18:00:00 +0000

“Angular or React?” is one of the most common questions in front-end development, and “or Flutter?” is now often added to it. The question sounds like a choice between three brands of the same product. It is not. Angular is a complete framework for web applications; React is a library for turning state into UI, which needs a framework around it to make an application; Flutter is a toolkit for mobile, desktop, web and embedded apps that does not use the browser’s HTML at all, but draws every pixel itself. Each has been described in detail in this section: What Is Angular?, What Is React? and What Is Flutter?. This article puts them side by side and ends with a guide to choosing.

What Is Angular? Google's Web Framework, From AngularJS to Signals

Tue, 20 Oct 2026 18:00:00 +0000

Most web pages are documents. Some are applications: a mail client, an analytics dashboard, a banking back office, a cloud console. Those have hundreds of screens, thousands of components and teams of dozens of people working on them for years, and building them directly on the browser’s DOM and event loop quickly becomes unmanageable. Angular is Google’s answer to that problem: a complete, opinionated framework that decides how such an application is structured, compiled, tested and shipped.