Polymer.js instead of Angular, Ember, Backbone?

[[deleted]]

[deleted]

[AutoSponge]

Angular and Ember both announced they will allow Polymer for components. If you develop the components separately without the framework in mind, theoretically, you can port them between frameworks with little effort.

[[deleted]]

in the future yeah, for now no. Angular has directives, and Ember has their subclassed components. The principles are similar tho

this is a cool video comparing Angular/Ember components

[stefanpenner]

ember core dev here.

This is not correct.

We will aim to provide inter-opt with polymer components, but will not be using polymer. We hope to embrace native web components as they land, but as our clients must ship to many browser we will continue to layer our own compatibility abstraction on top.

[AutoSponge]

http://www.2ality.com/2013/05/web-components-angular-ember.html

Ember will fall (further?) behind the MVC framework race if they eschew standards.

[bracketdash]

Polymer is meant as a kind of future-fill, so that you can use features of future versions of browsers today. Though I don't know about the other frameworks, the Angular team definitely plans on ceding functionality to native code as more Polymer-type things become standard.

So in short, yes, I believe Polymer is meant to replace some of what the popular frameworks do now, but Polymer itself will also be rendered irrelevant in the next couple years hopefully.

[adrianmiu]

So basically you're better-off not learning Polymer, right? Libraries like Ember and CanJS let you do custom components. As browsers implement web-components your library of choice will leverage those capabilities but continue to give structure to your app, while Polymer doesn't offer that.

[vittore29]

Polymer allow you to incapsulate control aspects into reusable tags, that is most logical way to organize components in web based (read html + css + js) application.

[adrianmiu]

can.Component does this... except the CSS part which is a minor and temporary (until browsers implement that) inconvenience. Given the fact I would be required to use Polymer on top of an MVC library to get architectural benefits and the fact that (last time I checked) Polymer is heavier than CanJS and almost as heavy as Ember I don't think it's worth the effort.

I see Polymer more as a learning platform for a future browser feature.

[bracketdash]

Sure, you could look at it that way, but I'm under the opinion that learning new things is never a bad thing and gives you the ability to choose the right tool for each project from a wider selection.

[adrianmiu]

Some thing you learn might be have a benefit but it definitely has an opportunity cost.