Not sure Dan's question was completely answered. Looks like there are two different teams at Google developing Polymer and AngularJS. Also appears that while the focus of each may be a bit different there is a good bit of overlap as well.
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? Thanks Steve On Sunday, November 9, 2014 at 4:39:37 PM UTC-6, Daniel Elebash wrote: > > Matt, thanks for replying > > That is good to hear but then will the team be adding features to polymer > such as routing or other advanced features to its core elements. A Road > map of planned features would be great!! > > I really like Polymer but just having a hard time deciding for Polymer vs > Angular 2.0 if the intent is for both of them to be Application Frameworks. > Then the question is why both. I would understand why both if the main > intent for Polymer is just building web components even though you use > those web components to build a complete Web App. > > The difference that I see is that Angular will have all of the core > features needed to build apps, these features are maintained by the Angular > team, of course people make add-ons, but for Polymer as it stands routing > is not a core feature, but an add-on by a third party. > > What can we expect from Polymer in the future in regards to core > functionality for web applications, things like form validation, server > validation. I know that core-input has validation but Angular makes it > easy to validate a whole form, and produces a error object. > > Another example Angular 2.0 data persistence > <https://docs.google.com/document/d/1DMacL7iwjSMPP0ytZfugpU4v0PWUK0BT6lhyaVEmlBQ/edit> > some > really nice and advanced features, are these types of features something > Polymer is intended to have in the core at some future date? core-local > storage is nice but not enough. > > There are many more of these types of examples that Angular handles, so > the question, does the Polymer team plan to add these types of core > features even in the form of core-elements or is it going to be up us? > Preferably it would be nice to have all the core features maintained and > tested by the team, like Angular does, with the community adding widgets > and other sugar. > > Thanks, > > Dan > > > > On Friday, November 7, 2014 11:38:20 PM UTC-5, Matthew McNulty wrote: >> >> You are incorrect. Polymer is a library that makes building components >> and applications easier, and is absolutely intended to be used to build >> everything from small components to large applications. Polymer is factored >> differently, into various elements above the core library, but the goal is >> indistinguishable from those of Angular. There are various ways to do >> interop as well, especially to use Polymer bits inside of an Angular app. >> But that's a side effect of the Polymer approach and not really an end goal. >> >> -Matt >> >> On Fri, Nov 7, 2014 at 5:42 PM, <[email protected]> wrote: >> >>> Still a little unclear as the direction of Polymer. >>> >>> Minus the polyfill part that will go away, is Polymer just a web >>> component building framework? Things like >>> layout,two-way-databinding,core-scaffold make it seem more than just a web >>> component building framework. >>> >>> So yes people can build polymer components that wrap ajax, and router >>> frameworks, but as far as long term Polymer core is not designed and will >>> not be designed to be an application building framework like Angular 2.0 >>> that will use web components and web components built using Polymer, >>> correct? >>> >>> Thanks. >>> >>> >>> >>> >>> >>> Thanks, >>> Dan >>> >>> On Friday, June 27, 2014 6:16:27 AM UTC-4, Pascal Precht wrote: >>>> >>>> Hi Mo. >>>> >>>> So these are a lot of question, I try to answer them one by one. >>>> >>>> > Polymer doesn't seem to address the problem of routing in a Single >>>> Page Application (although there appears to be a few fledgling attempts in >>>> the Web Components community to provide "router" elements). >>>> >>>> So, Polymer just uses Web Components polyfills under the hood and adds >>>> a small sugar layer on top of that to give a direction on how to uses the >>>> four specs (Custom Elements, Shadow DOM, HTML Templates, HTML Imports) in >>>> combination. In addition there are a lot of web components already >>>> implemented with Polymer (like paper elements or core element) to bring >>>> specific functionality to your web app via web components. >>>> >>>> In the end it's not polymer's job to provide web components that handle >>>> routing, *but* you *can* build web components with it, to make that >>>> possible. Just like things like `core-localstorage` etc. are not really >>>> *part* of Polymer but *built with* Polymer. >>>> >>>> > As far as I can see Polymer handles templating, data binding, data >>>> persistence (via "core-localstorage" etc), modularity (via HTML imports) >>>> and AJAX (via "core-ajax"). The only things that is missing is routing. >>>> >>>> Like mention above, doesn't really handle data persistence. >>>> `core-localstorage` is just an element built with Polymer to make data >>>> persistence possible via web components. Same goes for `core-ajax`. So, >>>> one >>>> can't really say that Polymer misses a web component that handles routing. >>>> >>>> > Most questions about how Polymer fits into other frameworks generates >>>> the response "They're just DOM elements, anything that understands the DOM >>>> will understand Polymer elements." This isn't strictly fair when we can >>>> already see that the Angular 2.0 templating will need some additional work >>>> to integrate with Web Components: https://github. >>>> com/angular/templating/issues/9 >>>> >>>> This is due to the fact that angular has it's own implementation to >>>> create custom elements (Angular Directives). Angular comes with its own >>>> kind of event loop to make two-way data-binding possible. These are not >>>> compatible with (native or custom) Elements per se. However, there are >>>> plans to make angular work with custom elements (that are not made in the >>>> angular world via directives) out of the box. You can read about it here: >>>> https://docs.google.com/document/d/1L-9bBL-smMrAmxC_ >>>> pVBdKWKcB-ZlOLTj-jmzAJ2jKeE/edit >>>> >>>> I hope this answers a few of your questions. >>>> >>>> /pp >>>> >>>> >>>> On Friday, June 27, 2014 11:37:33 AM UTC+2, [email protected] wrote: >>>>> >>>>> Hi all, >>>>> >>>>> I have a couple question about the future of AngularJS, specifically >>>>> about the upcoming 2.0 version, and how it relates to Polymer. I've been >>>>> through previous posts on the forums, articles about it on the web and >>>>> all >>>>> the answers I could find from last year. >>>>> >>>>> Polymer seems to focus on composition of elements on a page, these >>>>> elements can be visible or not and can have associated behaviour, >>>>> combined >>>>> with data binding and event dispatching it makes it very easy to share >>>>> state and trigger updates when information is changed. Polymer doesn't >>>>> seem >>>>> to address the problem of routing in a Single Page Application (although >>>>> there appears to be a few fledgling attempts in the Web Components >>>>> community to provide "router" elements). >>>>> >>>>> In the Topeka example application from the Polymer team, the "sign in" >>>>> view doesn't appear to have any kind of representation in the URL. No >>>>> hash-fragment, no direct way to reach that view. They do use HTML5 >>>>> pushState for history though, although this is manually wired up. >>>>> >>>>> As far as I can see Polymer handles templating, data binding, data >>>>> persistence (via "core-localstorage" etc), modularity (via HTML imports) >>>>> and AJAX (via "core-ajax"). The only things that is missing is routing. >>>>> >>>>> Most questions about how Polymer fits into other frameworks generates >>>>> the response "They're just DOM elements, anything that understands the >>>>> DOM >>>>> will understand Polymer elements." This isn't strictly fair when we can >>>>> already see that the Angular 2.0 templating will need some additional >>>>> work >>>>> to integrate with Web Components: https://github.com/angular/ >>>>> templating/issues/9 >>>>> >>>>> >>>>> Where does Angular 2.0 fit alongside Polymer if routing is addressed? >>>>> How will they work together? Does Polymer plan to enable support for >>>>> building Single Page Applications? >>>>> >>>>> >>>>> Cheers, >>>>> >>>>> Mo. >>>>> >>>> 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/3b605fda-8f00-452a-b7e9-51a4b8e00477%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/polymer-dev/3b605fda-8f00-452a-b7e9-51a4b8e00477%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/5b833b87-3292-4f45-81ab-825daa8ea043%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
