What are people's thoughts on this front? There are two major things I like about polymer: I think webcomponents are the future, and the paper components reference implementation of the material design spec is rad.
I'm examining options for building some large-ish angular stuff using material design tools (paper components will be the new bootstrap), and I'm looking at both ngMaterial[0] and a third-party binding library[1] to just integrate polymer webcomponents directly into angular. There's probably support at the implementation/support and performance level. On implementation, the pure-polymer route has that external dependency, but it is a pretty simple thing that is just there to make sure data binding works properly between webcomponents and the angular watchers. ngMaterial is being developed by some angular devs, but it also trails behind paper elements in some parts. ngMaterial also exposes handy-dandy services like $mdToast and $mdDialog. Perf-wise, I'm not sure if the ng-polymer-elements system introduces a real slowdown. It basically adds extra event listeners to hook ngModels in to the webcomponent, so extra step, but not a huge one probably. Ultimately, I'm personally leaning toward going with the polymer library rather than ngMaterial. My reasoning is that angular 2.0 is moving in the webcomponent direction (a big reason they're changing a lot of the syntax is to support webcomponent data binding) anyway and that the paper-core library will be better maintained than ngMaterial. What are your thoughts? Am I leaning in the wrong direction? [0]: https://github.com/angular/material [1]: https://gabiaxel.github.io/ng-polymer-elements/ -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
