Signals Are Gaining Traction

Most web apps still treat state like a black box: something changes somewhere, and the screen eventually catches up. Signals flip that around by making every dependency explicit, like wiring each light switch directly to the one bulb it controls. (angular.dev) Angular now teaches that model up front. In Loiane Groner’s April 8, 2026 course lesson on building an Angular Material header, the prerequisite material is already “the full signals model” of writable signals, computed signals, and effects, not the older mental model built around scattered class fields and manual updates. (loiane.com) A writable signal is the part you can change directly, like a thermostat dial. Angular’s own docs show writable signals as values you update with methods like `set` or `update`, which makes the source of change visible in one place. (angular.dev) A computed signal is the readout that recalculates itself, like a car dashboard estimating range from the fuel left in the tank. Angular describes computed signals as derived state that updates automatically when the signals they read from change. (angular.dev) That sounds abstract until you look at where it is spreading. Wagmi, the Ethereum app toolkit from the wevm project, now has a Solid version with its own getting-started docs under `wagmi.sh/solid`, which means the same wallet and contract data can plug into a signals-based user interface instead of only React-style hooks. (wagmi.sh) That is a bigger shift than a new framework adapter usually is. Wagmi describes itself as “reactivity for Ethereum apps,” and Ethereum frontends are exactly the kind of software where tiny updates matter because account balances, transaction status, and chain state can all change independently. (wagmi.sh) (wevm.dev) The Solid ecosystem is leaning even harder into this direction. The `solidjs/signals` repository says its standalone signals package is the reactive foundation of Solid version 2.0 beta, with first-class support for async work, transitions, optimistic updates, and reactive stores. (github.com) You can see why Ethereum tooling would care. A wallet connection changing should update wallet-dependent components, but it should not force unrelated parts of the page to rerun, the same way changing one train arrival board should not make the whole station redraw every sign. (wagmi.sh) (github.com) Angular is pushing the same idea from the other end of the market. Loiane Groner’s course page describes modern Angular as “signals-first state management,” and Angular’s official tutorials now go beyond writable and computed signals into “linked signals,” which keep a writable value connected to its source instead of breaking that relationship. (loiane.com) (angular.dev) When a framework course and a blockchain toolkit both start with explicit dependency tracking, developers begin to expect that shape everywhere. The likely result is more libraries exposing small reactive primitives with named inputs and outputs, and fewer libraries asking teams to trust one giant state container that updates by side effect. (loiane.com) (wagmi.sh)