Why I Am Excited About Polymer
The Promise of Object-Oriented Programming
The promise of OOP was to deliver complex applications by breaking up large and messy files into reusable and encapsulated pieces of code. Classes and objects that can be plugged-in to other parts of the application were designed to reduce the cost of creating and maintaining software. Over the years, and with the advent of techniques such as dependency injection, OOP has paid off in a many ways.
The Internet Shows Up
Enter Web Components
This is what Web Components and Polymer have set to solve. Formulated as a set of W3C standards, and slowly finding adoption among browsers, Web Components promise a new future for encapsulation and reuse, designed specifically for the web. It feels they are the missing OOP for the web.
Polymer is one of the first frameworks to implement web components and as such I am excited to see what it is capable of. Not every browser supports it yet, but most major browsers include it in their roadmaps. Simply put, Polymer is Google's way for creating Web Components, designed to allow anyone to define custom HTML elements. Using polyfills, browsers that currently don't support web components can display Polymer apps.
As part of the DC iOS Meetup series I spoke on Polymer and demonstrated a sample mobile and web application built with Google Polymer and Material Design. The event took place on Jan 7th at WeWork in Chinatown and it was broadcast via Goole Live Hangouts.