✳flâneur — a map of the web's best reading

React vs Signals: 10 Years Later - DEV Community

dev.to · 11,132 words · saved by 1 readers

In the past few weeks, we've seen the culmination of a build of excitement around the revival of fine-grained reactivity, being referred to as Signals, across the front-end world. For a history of Signals in JavaScript check out my article: The truth is Signals never went away. They lived several years in obscurity as third-party libraries or hidden behind frameworks' plain object APIs. Even though the common rhetoric that came in with React and the Virtual DOM condemned the patterns as unpredictable and dangerous. And they weren't wrong. But there is more to it than a 10 year old debate. So I want to talk about how things have changed over the years and offer SolidJS as a foil. At the core of this conversation is understanding what React is. React is not its Virtual DOM. React is not JSX. To this date one of my explanations on the subject came from one of Dan Abramov's earliest articles You're Missing the Point of React, where he state React's true strengths are: composition, unidirec

How does the old Winston Churchill quote go? Those who fail to learn from history are doomed to repeat it Although a more ironic addendum might add. Those who study history are doomed to stand by while everyone else repeats it. In the past few weeks, we've seen the culmination of a build of excitement around the revival of fine-grained reactivity, being referred to as Signals, across the front-end world. For a history of Signals in JavaScript check out my article: Article No Longer Available The truth is Signals never went away. They lived several years in obscurity as third-party libraries or

Explore this link on the map →

related reading