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
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




