Why you need to start using Polymer for your Web development

InfoWorld | Feb 25, 2016

Polymer enhances basic HTML in an easy, clean, and powerful way

Today I’ll discuss why people like the Google Polymer JavaScript library. The short answer is that Polymer makes it easier to create and use web components. To understand that, we need to dig a little deeper. HTML has about 100 standard components, such as div. Those don't really cover everything you want to do on Web sites. For example, you can’t change your page appearance over time. There are a variety of JavaScript libraries to enhance the capabilities of HTML, but having a capability in a library is not as good, or as modular, as having it in the browser.
As we've learned from long experience, adding a new component to the HTML standard requires the W3C committee to agree on a specification. and all the browser vendors to implement that specification. That can take years.
Instead of going through all that pain for every new component, why not have a single specification for custom components?
Web Components are a suite of draft specifications for the implementation of custom HTML components. There are 4 parts:
Custom elements is an API for registering your own implementations for HTML elements.
Shadow DOM encapsulates and hides the interior of a custom element inside a nested document. This is the most important part of Web Components and hardest to polyfill. (Polyfills are libraries that work around missing browser implementations.)
Templates enable you to store HTML data inside an HTML document. The content of a