Looks really great, Polymer has always felt a little heavy to me. Brick seems like it would fit in my workflow better. Web components are going to be revolutionary for the web, I can't wait until we can start leveraging them.
Can you explain why it feels heavy? I would love to know more.
Polymer's entire stack is a la carte:
* platform.js - polyfills if you just want to use vanilla web component apis, today
* polymer.js - build declarative custom elements that use data-binding, touch, property observation, inheritance
* elements (ui/non-ui) - if you don't want to write any code at all :)
Sugaring libraries like Brick and Polymer that sit on top of the native web component APIs will, of course, be opinionated and do things a bit differently. However, the workflow for consuming components will be similar across the board. Something like `bower install brick-carousel polymer-tabs`. Then use the elements in your pages.
X-Tag leverages the joint polyfill Google is the general maintainer of (Mozilla contribute code to it). It's the same one at the base of the Polymer stack.
Polymer, in comparison to Brick has a much more ambitious approach to being the framework to build apps with instead of aiding the creation of apps. Comparable with Dojo or .NET instead of jQuery.
The Polymer project from Google is something I've been following and I feel like it holds a lot of potential... Why hasn't it gained traction? Web components seem to be a great vision of the future of web design/development.
[+] [-] tyleregeto|12 years ago|reply
I don't see any mention of browser support?
[+] [-] ebidel|12 years ago|reply
Polymer's entire stack is a la carte:
* platform.js - polyfills if you just want to use vanilla web component apis, today
* polymer.js - build declarative custom elements that use data-binding, touch, property observation, inheritance
* elements (ui/non-ui) - if you don't want to write any code at all :)
Sugaring libraries like Brick and Polymer that sit on top of the native web component APIs will, of course, be opinionated and do things a bit differently. However, the workflow for consuming components will be similar across the board. Something like `bower install brick-carousel polymer-tabs`. Then use the elements in your pages.
[+] [-] yeukhon|12 years ago|reply
[+] [-] aravindet|12 years ago|reply
[+] [-] codepo8-hn|12 years ago|reply
Polymer, in comparison to Brick has a much more ambitious approach to being the framework to build apps with instead of aiding the creation of apps. Comparable with Dojo or .NET instead of jQuery.
[+] [-] mkelley82|12 years ago|reply
[+] [-] polskibus|12 years ago|reply