News for hackers. Stuff that matters.
Re:How Do the Google Web Projects Angular, Polymer and NG-Ma... by T-A on Saturday April 02, 2016 @02:35PM (#11412671)
My 10 000 foot view:

+ Polymer is a polyfill for the Web Components "standard" + a bunch of commonly needed components ready for use;

+ Angular 2 is designed to use Web Components "natively", without any need to wrap them up in Angular-specific code;

+ Material Design is just a look. You can style Web Components any way you want.

Disclaimer: I don't use any of the above. :D

Re:How Do the Google Web Projects Angular, Polymer and NG-Ma... by pax_americana on Saturday April 02, 2016 @06:52PM (#11413944)
Polymer is not a polyfill for the standards. It's just a library for creating web components in a less boilerplatey manner. The polyfill library is called webcomponents.js.
Re:How Do the Google Web Projects Angular, Polymer and NG-Ma... by T-A on Sunday April 03, 2016 @05:13AM (#11415477)
If you wish to be precise, webcomponents.js was broken out of Polymer a while back. See e.g. [1]. In practice, if you use Polymer you are still using the polyfill + the elements from the catalog, as exemplified on [2].

[1] https://github.com/Polymer/HTMLImports

[2] https://www.polymer-project.org/1.0/

Re:How Do the Google Web Projects Angular, Polymer and NG-Ma... by spankalee on Monday April 04, 2016 @11:52AM (#11422819)
You don't need the polyfills on Chrome.
Re:How Do the Google Web Projects Angular, Polymer and NG-Ma... by T-A on Tuesday April 05, 2016 @05:50AM (#11429150)
Sure, but as long as browser coverage looks like this,

http://caniuse.com/#search=components

you have to include the polyfills anyway, unless you are targeting something like Electron or an intranet where everybody is guaranteed to be using Chrome.

That's why I put "standard" in quotes; although it's been around for years, it's really only supported by one widely used browser.