Closed e111077 closed 8 years ago
@cdata communal worker seems to be using ES6 syntax. Should I convert it to the olden times?
I'm of a few minds on this. The primary use case for CommunalWorker (for us) is the same as the use case for SharedWorker: I have an offline-capable progressive web app, which implies I'm using ServiceWorker, which implies that I'm using a browser that supports the ES6 features currently found in the code.
That said, one could make the argument that CommunalWorker enables a SharedWorker-like feature for use cases beyond those tied to support for ServiceWorker. In that case, we should make the JavaScript as old-timey as possible. I'm open to that point of view.
@rictic do you have an opinion here?
One of the key features of a progressive web app is progressive enhancement. They use service worker where available, but a web app that requires service worker to function isn't very progressive.
So, I guess I'm saying that if we can make it useful on other browsers—or at least let it degrade gracefully so it doesn't bork the app if it's running on an older browser—we probably should.
That's a great point, @arthurevans . I think we have some ES6 -> ES5 conversion on our hands for the coming week.
As a Polymer app author guy, this element caught my eye. I gave it a go, but to much woe the docs really made me sigh