Why React Became My Front-End Framework of Choice

February 08, 2026 · in Frontend, Learning

I didn’t get into React because it was trendy. I got into it because it felt familiar.

Growing up, I spent a lot of time building with K’nex.
Once you understood what each piece did, you could build almost anything.

React feels the same.

Building systems, not pages

Front-end used to be about pages.

That works, until complexity builds. React changes the model. Instead of pages, you build systems of components.

Each piece is small, focused, and reusable.
Put them together properly, and the system scales.

That’s the same shift I had with K’nex:

individual parts are simple
the system they form is not

React removes a layer of friction. You don’t tell the DOM how to update.
You describe what it should look like.

State changes → UI updates. That sounds small, but it changes how you think.

You stop managing steps.
You start defining outcomes.

Components are where React becomes useful.

Each one:

Over time, you stop thinking in elements and start thinking in structure.

Good components make everything else easier. Bad ones make everything harder.

React enforces a direction:

data flows down, updates flow through state

That constraint matters. It makes behaviour easier to:

You’re not chasing side effects.
You’re working inside a system that makes them visible.

This matches how I approach problems:

React rewards that. It doesn’t remove complexity.
It organises it.

Frameworks change. This doesn’t.

React just happens to express those well. For me, it’s less a tool and more a medium. Understand the pieces, and everything else follows.