I tend to agree with you and share a similar dilemma as well. I've been playing around with Polymer for about a month now, as well as Angular 2.0 and ai must say, I have grown very "fond" of polymer. There's almost a certain finesse and elegance introduced to web development with web components and Polymer.
I'm about to start a large project with my team, and we almost refuse entirely to use Angular 1.x, because we see the glory of Angular 2 and we so want to bask in it. We have also talked about using Angular with Polymer as well, but just can't resolve to use Angular 1 because we actually want to write the UI for our apps with ES6. We see Polymer as a great platform for our UI, and Angular 2 as the "UI glue". But what do we do in this transition period (i.e. Angular 1.x to 2)? Do we use Angular 1.x when Angular 2 seems to be so close? On Friday, March 6, 2015 at 1:16:35 PM UTC-5, [email protected] wrote: > > Yes that does help quite a bit in understanding how these frameworks are > evolving. I appreciate your response. I would agree with your statement > that "Angular is a fine choice for building applications today" except the > 2.0 effort really gives me pause. Do I invest thousands of hours > developing a system on a foundation that is to completely change in the not > too distant future? Or instead do I invest in a newer framework (Polymer) > that may possibly better represent the future? > > I did find this post: > http://blog.sethladd.com/2014/02/angular-and-polymer-data-binding.html > that was really effective in illustrating strengths of both frameworks, > overlaps and how to get them to work together. > > I do appreciate that Google is full of smart people solving problems in > different ways. However, I perceive Google, as a customer, as one entity > that provides many services useful to me personally and professionally. > I'm hopeful that soon Google will communicate a consolidated, cohesive > vision for web application frameworks. Don't get me wrong, I'm > appreciative of the work that's being done, it just gets difficult at times > to sift the best choices out of the plethora of technology stack choices. > > > On Thursday, March 5, 2015 at 11:14:41 PM UTC-6, Matthew McNulty wrote: >> >> >> Google vends many products and technologies, and is a relatively large >> company full of smart people with lots of different ideas on how to solve >> similar problems. There is no singular Google opinion or singular picture >> Google is painting as a whole. >> >> Angular is one of the best of the current generation of JS frameworks. It >> is a fine choice for building applications today. >> >> Polymer is the first of a next generation of technologies that posit a >> future where there does not have to be an additional framework layered on >> top of the web platform, because the platform itself is much more >> functional now that it has web components. The framework is DOM. We like to >> say this is like what should have happened if the web platform had kept >> evolving naturally and not gotten stuck, and a JS-heavy apparatus strapped >> on top. Polymer is markup- and DOM-centric. >> >> Polymer is useful for building custom elements or applications. Elements >> built with Polymer can easily serve as leaf nodes in applications built >> with web component-friendly frameworks like Angular 2. >> >> Polymer is part of the Chrome team, and as a result embraces the platform >> and web components in an idiomatic manner. This is also why you see Polymer >> featured at events like Chrome Dev Summit and Google I/O. Angular is a >> separate effort by a different team at Google with no relation to Chrome. >> >> Hope that helps. >> >> -Matt >> >> On Thu, Mar 5, 2015 at 7:49 PM, <[email protected]> wrote: >> >>> > "Perhaps this is a not a question for a Polymer forum but what is the >>> picture that Google is painting relative to these web frameworks? For a >>> new web application development effort what foundation would Google suggest >>> to build upon? Polymer, AngularJS, some hybrid?" >>> >>> Exactly this. >>> >>> I'm trying to decide between the myriad frameworks, and Angular/2.0 >>> seems the most compelling. However, after reading this thread, the purpose >>> of Polymer and its relationship to Angular is confounding. >>> >>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Polymer" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/polymer-dev/2dc1f504-0706-4e66-b3b8-946c83f92279%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/polymer-dev/2dc1f504-0706-4e66-b3b8-946c83f92279%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/7a534af6-e8d0-4520-9d90-a06dbcc62cee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
