>>I'm using angular and have only skimmed to documentation for polymer - superficially at least they look very similar in capabilities. Why do you prefer polymer ?

I believe that polymer (is the 'p' suppose to be uppercase?) is the next logical step from Angular. 'polymer' creates new html elements which are web components designed by the programmer. So anything that runs html5 will work - almost any device that connects to the internet has html5. So how is this different than Angular's directive? I don't see the difference. Therefore, I see polymer extending Angular's directive to the next step. Google must see it the same way or why develop polymer.

Currently there is a down side to polymer. polymer requires polyfill and that means it is slower than Angular. But I believe that all the browsers will provide polyfill in their code. Chrome will soon have it built-in. Also unlike directives polymer elements will be shared just like web components are today or there will be commercial lib's available.

Johnf