The Frontend Framework Landscape

Written by Backbone Tutorials Team

Last updated: June 2026 · 10 min read

The phrase "frontend framework" covers tools that differ enormously in what they actually do for you. Some hand you a few building blocks and let you assemble the architecture yourself; others provide an entire opinionated structure with routing, data fetching, and build tooling included. Choosing well means understanding which kind of help you are signing up for, because the right tool for a small widget is the wrong tool for a large product, and vice versa.

This guide maps the landscape by what each family of frameworks provides, compares their core approaches, and places Backbone.js within it.

What a frontend framework actually does

At its core, every frontend framework exists to keep the user interface in sync with application state, and the differences between them are mostly about how much of that work they take off your hands.

The core problem they all solve

State changes constantly in a real application: a user types, data arrives, a selection updates. The framework's job is to make sure the screen reflects that state without the developer manually editing the DOM for every change. A minimal library gives you the pieces to do this yourself, while a comprehensive framework does most of it automatically. Everything else, routing, data fetching, build tooling, is a layer on top of this one responsibility.

The major families of frameworks

Frameworks cluster into a few families defined by how much structure they impose, and knowing the families is more useful than knowing every individual tool.

From libraries to full frameworks

Libraries like Backbone give you primitives and expect you to assemble the architecture. Component frameworks like React and Vue provide a declarative rendering model but leave choices like routing open. Full frameworks like Angular, Next, and Nuxt bundle routing, data, and build tooling into one opinionated package. Compilers like Svelte and Solid move work to build time. The trend across this framework evolution has been toward providing more structure by default.

Rendering models compared

How a framework turns state into pixels is one of its defining characteristics, and the approaches have real performance and complexity consequences.

Virtual DOM, reactivity, and compilation

React uses a virtual DOM, computing what changed by comparing a description of the new interface against the old. Vue and Solid use fine-grained reactivity, tracking exactly which values each part of the interface depends on. Svelte compiles components into direct update code with no runtime diffing at all. Backbone did none of this, leaving the developer to call render, which is precisely the work the others automated. The mechanics are detailed in reactivity systems.

How frameworks manage state

State management is where frameworks differ most in day-to-day use, and it is often the deciding factor in a large application.

Local state, stores, and the evolution of patterns

Small applications keep state local to components, but as data needs to be shared, frameworks reach for stores: centralised state containers that any component can read. The patterns have evolved considerably, from Backbone Models and Flux to modern signals-based stores, a progression covered in state management evolution. The choice of state approach often matters more for long-term maintainability than the choice of framework itself.

Choosing a framework for a project

The right choice depends on the project, the team, and the timeline far more than on which framework is currently fashionable.

Matching the tool to the situation

A small interactive widget on an otherwise static site may need only a tiny library or no framework at all. A large product with many engineers benefits from the shared conventions a full framework provides. The team's existing knowledge matters too: a framework everyone knows ships faster than a marginally better one nobody has used. A structured way to weigh these factors appears in frontend framework comparisons.

Where Backbone fits in the landscape

Backbone occupies the library end of the spectrum, and understanding its position clarifies the whole map.

The minimal end of the spectrum

Backbone provides Models, Views, Collections, and a Router, then steps back and lets you build the architecture. That minimalism was its strength when the alternative was unstructured jQuery, and it is why Backbone is no longer a default when fuller frameworks exist: it deliberately does less. As a teaching tool it remains valuable precisely because its small surface, explained in the Backbone.js guide, exposes the problem that every framework further along the modern frameworks spectrum tries to solve.

Read next: comparing frontend frameworks, or the Modern Frameworks hub.