liveBook · Manning

Framework

As explained in Web Components in Action

A software framework is a reusable application structure that provides conventions, abstractions, and extension points for development.

A framework organizes application development around selected conventions, abstractions, and extension points. Choosing one depends on the project and team: a straightforward application may benefit from a modern framework, while another may be constrained by it. section 1.4

Frameworks commonly distinguish themselves by the application features they choose to provide:

  • Data binding, routing, and MVC-style application design are framework-level choices rather than native Web Components features. section 14.1
  • Frameworks can align tutorials and examples around a consistent application pattern, helping beginners work with related features together. section 14.1
  • Framework features and libraries can remain interchangeable: Redux may be used beyond React rather than being permanently tied to it. section 14.1
Figure 14.1. Deprecated data binding feature: Object.observe

Use this deprecated browser feature as a cautionary example of a proposed native data-binding foundation that frameworks did not broadly adopt. section 14.1

How Web Components in Action covers it

How deep it goes
Compares framework responsibilities and trade-offs but stops short of implementing a particular framework.
Examples
Uses Redux and React, plus deprecated Object.observe, to illustrate interchangeable libraries and rejected native data binding.
What it assumes
Assumes awareness of web projects and Web Components while contrasting native features with application-level conventions.
What you can do after
Evaluate framework and no-framework options against project needs and recognize their standards-based underpinnings.
How it connects
Connects frameworks with Web Components, data binding, routing, MVC, application state management, Redux, and React.

Also explained in

Compare how 5 books explain framework →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Web Components in Action. The section links point to the parts of the book it draws on.