On Thursday, March 5, 2015 at 10:41:38 PM UTC-8, Matthew McNulty wrote: > > > > On Thu, Mar 5, 2015 at 10:23 PM, Artem Khodyush <[email protected] > <javascript:>> 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. >
Oh, I thought 0.8 is not like any other version - I thought there was a reason why many features from 0.5 are missing in 0.8-preview. But you are the boss :-) > >> >> 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. >>> >>> -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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/polymer-dev/f602ae19-2ddd-45c9-89b7-f2f4e64df143%40googlegroups.com >> >> <https://groups.google.com/d/msgid/polymer-dev/f602ae19-2ddd-45c9-89b7-f2f4e64df143%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/74df2dd6-2c93-4890-bc7b-1779c1d0fad4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
