Menu
I understand Chrome is becoming complete in terms of Web components requirements.
Does that mean Polymer is no longer strictly needed?
583
Web components are a set of APIs that lets you create native, isolated components to be used anywhere regardless of the framework, library or whatever is out there. Custom components is being used the same as real native components like inputs and buttons.
Polymer is an open-source JavaScript library for building web applications using Web Components. The library is being developed by Google developers and contributors on GitHub. Modern design principles are implemented as a separate project using Google's Material Design design principles.
POLYfill is Polykemi's product family of plastic compounds based on polypropylene, a rigid thermoplastic characterized by a low density and high chemical resistance.
The Polymer library provides a set of features for creating custom elements. These features are designed to make it easier and faster to make custom elements that work like standard DOM elements. Similar to standard DOM elements, Polymer elements can be: Instantiated using a constructor or document. createElement .
To be clear, the platform.js layer (the polyfills) go away as native support becomes available in browsers, but polymer.js (sugaring layer on top of web components) and the elements will not. The sugaring is Polymer's opinion on how to use the web components++ tech together, and the elements are generally useful/reusable components.
This post describes the pieces of Polymer: What is the difference between Polymer elements and AngularJS directives?
Today, it's not strictly true that you can use polymer without including the platform.js polyfills. We're working on making that possible now that there's one browser will native web components support. We're not quite there yet e.g. you still need to include platform.js in chrome 36.
88
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
