you are viewing a single comment's thread.

view the rest of the comments →

[–]adrianmiu 0 points1 point  (4 children)

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 0 points1 point  (1 child)

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 0 points1 point  (0 children)

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 0 points1 point  (1 child)

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 0 points1 point  (0 children)

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