What’s up with Polymer and Web Components? Those terms have popped up onto my radar since the start of the year or so. I bet you’re starting to see them more as well. I think most of the posts are tweets and presentations from Google developer relations folks that I follow on Twitter. From what I understand this is a W3C spec and I wonder if it’s DOA looking to crash into a dead end, or if it’s the very future of building websites in a modern way. What do you think?
What Am I Searching For?
From my stand-point I look at it two ways:
- Can we in the open-source community better share each other’s work at the UI/DOM level via new first-class HTML citizens that we create no matter the inevitably conflicting underlying JavaScript tech stack?
- Can I get away from the ever increasing entropy which is jQuery’s venerable 8-year old age that’s served us well in it’s triumvirate set of (css selectors + AJAX + plugins) that’s smelling more stale each month
- What parts of a single-page web-app technology stack are made obsolete
Watch and Read These
Here are some references that I’m looking towards while learning more about the W3C spec in progress “Web Components” and Google’s cross-browser compatibility layer (aka shim) called the “Polymer” library upon which we can build tomorrow’s browser foundational features now.
Videos
- Polymer & Web Components Change Everything (Eric Bidelman)
- Componentize the Web (Addy Osmani)
- Unlock the Next Era of UI (Rob Dodson)
- Polymer and the Web Components Revolution (Matt McNulty)
- Introduction to Polymer (Matthew McNulty)
Pages
Projects
- Custom Elements
- Google Web Components
- Addy Osmani Web Components Talk
- Google Demo App – “Topeka” Quiz
Have a Coffee and Give it a Think
Watch and read these over a coffee. Ping me on Twitter when you have something to demo and I’ll gladly celebrate your success with you. Let’s do something awesome together!
