Why Web Components?
The objective of Web Components is to alleviate the Composition Problem, which is a part of the larger Multiple-Actor Problem.
Desired results:
- fewer breakages when changing out middleware or UI parts of the web app, or when adding third-party components
- thriving, open ecosystem of mix-and-match components from various vendors
Idea: let's make it easier to build components that are truly reusable across frameworks.
Problem: it is impossible to make all frameworks, future and past, arrive at and agree on a common contract.
Proposed Solution: Since every framework (aside from canvas/rendering ones) relies on DOM, in order to be reusable, your components should be indistinguishable from HTML/DOM elements.
- Custom Elements: a component is an HTML element.
- Shadow DOM: hide implementation details of an element (nee component) in the same way the HTML elements hide theirs.
Polymer and Angular 2 at ng-conf Keynote
