Introduction to Polymer: The Next Generation of Web Development - Matthew McNulty

Polymer's declarative syntax makes it simpler to define custom elements. Features like two-way data binding, declarative event handlers, property observation, and gesture support help you build powerful, reusable elements.

[patrickh.]

+1 This is one of the best explained video about Polymer and the things behind it.

These are the important facts:

- Polymer ...
 - ... is a sugaring library on top of the Web Components spec defined by the WHATWG
 - ... uses native Web Components if they're supported by the browser
 - ... uses prolyfills for the Web Components (Custom Elements, HTML Imports, Shadow DOM) build by the same people who building Polymer
 - ... is NOT a polyfill, it uses some polyfills and sugars them as well
 - ... adds also data binding, ES6 polyfills, ...

- Shadow DOM ...
 - ... brings classes to the web platform (not javascript!)
 - ... adds no security
 - ... enables style encapsulation

- Polyfills focus on compatibility, not performance
- Mozilla's X-Tag is an alternative to Polymer, but also uses the same platformjs/webcomponentjs
- Web Components are low-level
- The Component Model (as described in XBL 2 back in the history) equates to Custom Elements spec

Polymer's philosopy:
 - Separation of concerns
 - Everything is an element (visual and non-visual elements)
 - Composition (enabled by Shadow DOM) of various elements creates a new one: small components -> bigger components -> applications
 - DRY: Don't repeat yourself
 - Write only code, unique to your app

[DerekBraid]

Regardless of your opinions or experience with web components and various front-end frameworks this is a solid talk worth viewing for web developers.

[lyderiscom]

6:17 And in my opinion, actually, too much talent
6:20 is being spent working on frameworks,
6:22 papering over deficiencies in the platform.
6:26 And it's time to change that.
6:28 It's time to give those people the ability
6:30 to build stuff beyond frameworks that's actually interoperable.
6:35 So a brief word about Polyfills.
6:38 So Eric touched on this briefly.
6:41 The Polyfills are kind of a bridge
6:42 to the future that's available right now.

[slothsarecool]

MXML? I think lots of platforms have already been down this road, not arguing it one way or another, but there's certainly pros and cons. I'd be bummed to see people writing element-first APIs, IMO they should be akin to something like middleware, where you write a good js api, then wrap it in middleware, not write strictly for middleware.

jQuery options object first design is another funky example of where that stuff went pretty wrong (IMO).

[SambhavSharma]

Couldn't they have built a Component library over or for Angular instead?

[TheVBounce]

I actually liked his web presentation. Does anyone know how he did it?

[ojumle]

Why u are using deprecated Shadow DOM v0 API for Youtube?!

[JuanDavidPastasRivera]

it seems not the easiest thing to learn.

[DMZ]

I'm so happy I'm not a web developer.

[calebprenger]

in some of my research, these things are bloated and hurt SEO

[amangupta]

Whit this extension you can read comments while watching video on YouTube and more..

Auto turn off lights, when mouse stays for more than 2 seconds on the video player.

By Right click of the mouse you can search any selected Phrase or Text on YouTube while surfing on Internet.

You can search videos on the sidebar without stopping playback of the current video (Search YouTube videos in the background).

[pdiddles]

This is all cool and what not, but the thing is, think about your average web developer.  They have no idea what you are talking about, or the benefit of this.  So it will never be used.