An application need not commit every feature to one framework. Interoperability is the ability to use code across those boundaries: a primarily Vanilla Web site can add a framework component where requirements call for one, while continuing to use browser-native code elsewhere. This flexibility can be harder to recover in an application that expects every feature to belong to its framework. section 2.5.2
Web Components provide a portable component boundary. A component built on HTML, CSS, and JavaScript can be shared between framework-based and framework-free projects without depending on a particular library. This does not make framework-specific components equally portable. section 7.1 section 7.3
Choose tools feature by feature
A Vanilla Web site might mount a React component in one section, use a Chart.js graph in another, and draw directly to a WebGL canvas elsewhere. A Web Component for a rating widget or modal dialog can then be shared with projects using React, Angular, or no framework. section 2.5.2 section 7.1
Keep reusable components independent of a framework when cross-project use matters. Custom elements participate in normal browser events, CSS selection, accessibility attributes, and developer-tool inspection. Shadow DOM can additionally isolate internal markup and styles when that boundary is useful. section 7.3








