Data binding synchronizes application data with a user interface or component state. Frameworks commonly provide it alongside MVC patterns and other application-structure features, while plain JavaScript and Web Components leave the choice of pattern to the developer. section 1.3 section 14.1
Use data binding as one option within a broader application data-flow design:
- Choose a framework when its data-binding and state-management conventions fit the application. section 1.3 section 14.1
- Prefer simpler JavaScript patterns when a larger framework would add unnecessary structure; an event bus can route changes between distant components. section 1.3
- Treat native data-binding support cautiously: Object.observe was deprecated and was not adopted by popular frameworks for their state-management solutions. section 14.1
A component hierarchy
A color picker can contain text inputs and sliders whose changes reach the parent component, which then reports the resulting color to its parent. As components become separated in the DOM, direct event bubbling may no longer suit the data flow, making a different coordination strategy useful. section 1.3
Inspect the deprecated Object.observe approach as historical context for native JavaScript data binding. section 14.1




