SolidJS vs. React: The Go-to Information

On the floor, SolidJS and React seem like intently associated. The client-side frameworks are mutually intelligible and are each used to create single-page functions (SPAs). Whereas the developer expertise is almost similar for each, the underlying mechanisms of every framework are a outstanding distinction.

Each SPA frameworks are chargeable for compartmentalizing an app’s webpage construction and performance, however in a browser, these frameworks manipulate pages’ HTML parts otherwise to ship the specified consumer expertise. SolidJS and React diverge of their use of the Doc Object Mannequin (DOM). Let’s develop on how React and SolidJS parts permit software logic to imitate a multi-page web site.

A Temporary Comparability

I’m a agency believer in a TL;DR method, so I’ve boiled down and introduced React and SolidJS’s important variations within the following desk:




TypeScript help

Declarative nature

Unidirectional knowledge stream

JSX first-class help

Direct manipulation of the DOM

Avoids part re-rendering

Extremely performant

Wealthy neighborhood and ecosystem

Glorious developer documentation

Scaffolding instruments

Conditional rendering

Server-side rendering (i.e., hydration)

Concurrent rendering (i.e., suspense)

Now we’ll go into extra element on the similarities and variations between React and SolidJS.

Part Construction

React and SolidJS have precisely the identical programmatic constructions and help for parts (particular person, reusable items of code).

In each fashionable React and SolidJS, a part consists of a render perform with properties as arguments. Along with every part’s JSX, the code is tight and succinct. JSX is straightforward to grok, and permits skilled builders to visually describe a part’s mannequin in its definition.

React and SolidJS provide the identical parts, however every framework has a singular rendering method. React parts render each time (barring memoization use), whereas SolidJS parts solely render as soon as.

See also  Taloflow with LV Jadavji - Software program Engineering Day by day

One other distinction between the 2 frameworks is their various options that allow part performance.

Part Performance

A part with out performance is simply markup. So how do React and SolidJS make parts operational? Their approaches are comparable:






use (e.g., useState)

These are features supposed to run when triggered by the framework at particular instances in a part’s lifecycle.

Hook features are unbiased from each other, however can name different hooks from throughout the identical part. Such name chains permit for extra complicated performance and for code to be composed into subfunctions.


Reactive primitives

create (e.g., createSignal)

These are features whose APIs are much like these of hooks.

Below the hood, each hooks and reactive primitives are a approach to join into the respective React and SolidJS change administration methods. Total, the 2 frameworks deal with part features in the same method, however make use of completely different strategies or nomenclatures to take action.

Let’s discover extra complicated performance variations: state, memoization, and results.


At instances, a framework might want to monitor info and sure properties tied to a part. This idea is called state, and could be accessed in React with the useState perform. In SolidJS, this idea is called sign, and its corresponding creation perform is createSignal.

States and alerts home part knowledge (within the type of props), enabling the framework to trace worth adjustments. And when the framework detects a change, the part is rendered with the in accordance worth(s).


An impact is a particular perform that could be a core constructing block in each React and SolidJS. As a substitute of responding to a direct consumer interplay with the browser, an impact is triggered when a part state adjustments, akin to a callback or occasion listener.

React defines an impact with the useEffect perform, whereas SolidJS makes use of the createEffect perform.


Memoization optimizes framework efficiency by caching expensiֵve part render outcomes, and utilizing cached values when acceptable versus recomputing values. In React, we implement memoization through the use of considered one of three hooks:

Memoization Hook

Used With


Pure parts


Elements that depend on perform props


Costly operations and part operations

React relies on memoization for its functions to render shortly. In distinction, due to its optimized change monitoring and DOM utilization, SolidJS hardly ever requires express memoization. For excessive edge circumstances during which part prop adjustments don’t entail a rendering replace, SolidJS manages memoization by way of a single technique known as createMemo.


SolidsJS and React have efficiency variations that attain past their approaches to memoization. The 2 languages method HTML manipulation in very alternative ways. The focus of this distinction is how every updates the browser DOM.

React’s founder gave it a light-weight digital DOM to interface with the browser’s precise DOM. React’s code causes its personal digital DOM to replace as parts render. React then compares the up to date digital DOM towards the browser’s DOM, and the recognized adjustments bleed by way of into the precise web page construction (i.e., the DOM).

We might argue that—as a result of React re-renders parts by default, counting on DOM distinction calculations for updates—React is doing its work twice. Because it renders parts each time, React requires memoization to keep away from pointless, repetitive computations.

In distinction, SolidJS’s founder managed to dodge all of this round-tripping. By utilizing a mechanism known as fine-grained reactivity to instantly manipulate the browser’s DOM, SolidJS delivers a a lot lighter reminiscence footprint and a blazingly quick software of web page edits and injected code.

Nice-grained reactivity tracks variable interdependencies. Primarily based on variable dependency and edit chains, SolidJS limits our web page construction updates to replicate solely what has modified, bypassing pointless part renders. This leads to a large efficiency enchancment over React.

Although I’m tempted to finish the article right here and say that SolidJS is the clear winner because of its speediness, it stays vital to debate how the 2 frameworks stack up by way of developer effectivity.

Developer Productiveness

There are a number of key concerns once we take into account developer productiveness in React versus SolidJS:




Figuring out and monitoring part dependencies

Manually tags part dependencies with useEffect.

Robotically detects and tracks part dependencies.

Destructuring properties inside render or hook definitions

Helps this characteristic.

Doesn’t help this characteristic out of the field, however this utility mission bridges the hole.

Utilizing state parts with out markup

Requires extra scripting to implement a shared state between a number of parts.

Helps this effectively and natively.

A assessment of your mission’s particular use circumstances can reveal which framework is a more sensible choice, productivity-wise.

SolidJS vs. React

I’ve appreciable expertise with each SolidJS and React. From my perspective, SolidJS is the clear winner of the 2. SolidJS matches React’s energy and sturdy options. Furthermore, it delivers a brisk responsiveness to finish customers that’s unmatched by React.

For a React developer to stand up to hurry on SolidJS, which leverages the teachings, construction, and summary approaches realized over React’s lifetime, there may be virtually no studying curve. I’d suggest you begin utilizing SolidJS at present—it could be the way forward for entrance finish.

The editorial workforce of the Toptal Engineering Weblog extends its gratitude to Yonatan Bendahan for reviewing the technical content material introduced on this article.

Additional Studying on the Toptal Engineering Weblog:

Leave a Reply