Progressive, Performant, Polymer: Pick Three - Google I/O 2016

[@DoctorReefer]

Awesome talk. You summed it up perfectly!

[@marcusjt]

An awesome, inspiring talk, thank you!

[@pepelsbey]

Google I/O 2016 pasted twice in the video title

[@mbxmusic7028]

Would it be possible to make an app that progresses to something completely different, and to another app with other dependencies and then go on like that without any performance issues? Will the garbage collection handle that?

[@alexpolymath]

Cool, but HTML Import is not supported by Edge, Firefox, Sarafi, iOS Safari yet. And even worse situation with Service workers. How much it will take for browsers to inject all this cool features?

[@romaindurand]

There are polyfills for html imports. A progressive web app must work even without service workersthat's just a feature that allows offline browsing and better cache policy. Other browsers will follow if they see a massive adoption of service workers, they don't wan't to be known as "the slow web browser".

[@SectionF4]

Everyone but Apple seems to be slowly getting on board with html imports. Wish I knew what their apprehension was about in regards to adding the feature. It's a pretty key part to Polymer.

[@DanDascalescu-dandv]

Actually Service Worker is supported by Firefox and Opera. See jakearchibald.github.io/isserviceworkerready/

[@romaindurand]

If custom elements are available via polyfills, why should I use Polymer ?

[@GrahenKraken]

The polyfills only 'fill' the APIs, but Polymer gives you a nice declarative syntax to make your life easier, along with some other bits like data-binding etc.

[@juanluisclaure6485]

amazing now we can use purple pathner. it is all in beta but defently is the way how future comes in internet

[@MartinHotell]

right, right, right, right 1000 times