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.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/cbc9f816-1e03-4d67-a170-bcdb38ccc621%40googlegroups.com.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 polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAHbmOLYWrFw5RqNXmZQLRwr068bYtsAgR0fK6eYN-cOsa3g83A%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/df1809b5-5900-408a-a4ea-6e3e84990f03%40googlegroups.com.
We'll be building an app around a more full featured app like Topeka in the future, but nothing yet.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/378c73cc-e9a8-47ad-a74c-17f708808059%40googlegroups.com.
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 polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/3b605fda-8f00-452a-b7e9-51a4b8e00477%40googlegroups.com.
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 polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/2dc1f504-0706-4e66-b3b8-946c83f92279%40googlegroups.com.
> 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.This immediately brings a question: could you clarify your intent with regard to other browsers? Are you going to make sure that production-ready Polymer (promised to appear relatively soon AFAIR) will work equally well across major browsers?
Does 0.8 mark the end of big push to move Web platform forward with Polymer, and if so, what's coming next (you said Polymer is the first of a next generation of technologies)?
Follow Polymer on Google+: plus.google.com/107187849809354688692
On Thursday, March 5, 2015 at 9:14:41 PM UTC-8, 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.-MattOn Thu, Mar 5, 2015 at 7:49 PM, <trefigh...@gmail.com> 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?"Follow Polymer on Google+: plus.google.com/107187849809354688692Exactly 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.
---
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 polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/2dc1f504-0706-4e66-b3b8-946c83f92279%40googlegroups.com.
---
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 polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/f602ae19-2ddd-45c9-89b7-f2f4e64df143%40googlegroups.com.
On Thu, Mar 5, 2015 at 10:23 PM, Artem Khodyush <gree...@gmail.com> wrote:> 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.This immediately brings a question: could you clarify your intent with regard to other browsers? Are you going to make sure that production-ready Polymer (promised to appear relatively soon AFAIR) will work equally well across major browsers?Polymer works best on Chrome because it natively supports web components. Polymer works reasonably well on other evergreen browsers - nearly as well as (but not equal to) Chrome with Polymer 0.8.Does 0.8 mark the end of big push to move Web platform forward with Polymer, and if so, what's coming next (you said Polymer is the first of a next generation of technologies)?0.8 marks the end of the development of 0.8, like any version. 0.9, 1.0, 1.1, etc will follow along. Polymer will continue to push the envelope on the web platform - this is our mission. Web components are only the first step. The web platform is constantly moving forward, and there are new features like Service Workers, ES6, Push Notifications, etc to incorporate, shape, and get in the hands of as many developers as possible via Polymer. This is only the beginning.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/2d22d30a-dea1-498b-b9da-8bb74fba762c%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/7a534af6-e8d0-4520-9d90-a06dbcc62cee%40googlegroups.com.You received this message because you are subscribed to a topic in the Google Groups "Polymer" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/polymer-dev/fAvqDo40tMk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to polymer-dev...@googlegroups.com.