Opening Keynote (The Polymer Summit 2015)
Why Stack Overflow recommends it
Stack Overflow users link it when answering whether Polymer is a framework or a toolkit, since it explains the team's 'legos' philosophy and the planned Carbon app-level elements.
Recommended by 1 people across 1 different months, 2015 to 2015.
What it is
The opening keynote of the first Polymer Summit in 2015, given by Polymer product manager Taylor Savage. It covers how the Polymer core team thinks about the library's past, present and future, including its role relative to full frontend frameworks.
What people said
Recommends Kayce Basques · 2015-10 · Stack Overflow · on “Polymer 1.0 main html document structure”
Taylor Savage (Polymer Product Manager) addresses this in the Polymer Summit 2015 opening keynote [this video] (the video is timed to kick off exactly where Taylor discusses the topic). Up to now the Polymer team has viewed Polymer as "legos". You can put them together however you want. E.g. if you want routing, you can wrap your favorite routing library in an element. Polymer is a "swiss army knife" of tools that you use as you need. It's not a framework. It doesn't enforce app-level architecture. It's up to you decide. Which makes it hard on developers to know where to start. So, here's three options off the top of my head: Design your own architecture however you see fit Wait for the "Carbon"
Cites RationalDev likes GoFundMonica · 2015-06 · Stack Overflow · on “Is Google's Polymer a fully functioning Frontend Framework to Subsitute OR Complement other Frontend Frameworks?”
From the Polymer Starter Kit [LINK] : " Framework-free, or framework-compatible Build your app out of elements, or wire in an external framework to handle business logic. It's up to you!" Update: What was described as Carbon Elements seems to fall under: Polymer(version 2) App Toolbox [LINK] Component-based architecture using Polymer and web components. Responsive design using the app layout components. Modular routing using the elements. Localization with <app-localize-behavior> . Turnkey support for local storage with app storage elements. Offline caching as a progressive enhancement, using service workers. Build tooling to support serving your app multiple ways: unbundled for delivery ove
Cites Michael Ben-Nes · 2015-11 · Stack Overflow · on “Is Google's Polymer a fully functioning Frontend Framework to Subsitute OR Complement other Frontend Frameworks?”
Surprise. It seems that a new group of elements (Carbon) will be introduced. Group that will provide solution for layouts, routes and etc. I guess it will be more like a library on steroids. [this video]