3 ms·

That's cynical. You must have your own bugs every now and then. This is no different. PS: google employee, used to work with torne every now and then, but no s

That's cynical. You must have your own bugs every now and then. This is no different. PS: google employee, used to work with torne every now and then, but no stake in the conversation anymore.

dmitriid 7y ago
Cynical? Yes. Is that the state of the world? Yes. Browsers are platforms that are as complex as OSes these days. And any bugs or changes in how they work will affect you app if your app is PWA. - It could be Chrome breaking audio: https://danshumway.com/blog/chrome-autoplay/ https://danshumway.com/blog/chrome-autoplay/ - It could be Chrome breaking LocalStorage: this discussion - It could be Chrome removing support for a web standard that was implemented and shipped: https://www.chromestatus.com/feature/4642138092470272 https://www.chromestatus.com/feature/4642138092470272 I'm linking Chrome issues here because Chrome is the most visible of all browsers with the largest marketshare, but other browsers have their issues, too.
- bzbarsky 7y ago
  Just to set the record straight on the part I'm familiar with, "Custom Elements V0" was never a web standard. It was a proposal, which Chrome implemented and shipped without getting everyone else on board, and which turned out to have significant enough problems that a somewhat different thing got standardized and shipped in all browsers ("Custom Elements V1").
  - dmitriid 7y ago
    Once something is shipped, people will rely on it. For example, quite famously, Youtube did for a very long time (until this year IIRC). AMP used to use it. There are several polyfills available. Several Polymer versions targeted v0. Etc. etc. It's not specifically Google's fault that they are removing support for these, but, once again, that's the state of the world: browsers are lrage complex platforms that may and will break your app.
    - bzbarsky 7y ago
      Sure. Unshipping things is always hard, and likely to break people. But there's still a difference between unshipping support for a standard and unshipping support for a non-standard technology that only you ever implemented. In the latter case, people should be a lot more wary of depending on the technology in the first place. While it's true that browser updates may break your app, it's also true that there are ways to write the app so as to minimize the risk of such breakage. Using Custom Elements V0 was _not_ a good way to avoid potential breakage...

That's cynical. You must have your own bugs every now and then. This is no different. PS: google employee, used to work with torne every now and then, but no stake in the conversation anymore.

dmitriid 7y ago

Cynical? Yes. Is that the state of the world? Yes. Browsers are platforms that are as complex as OSes these days. And any bugs or changes in how they work will affect you app if your app is PWA. - It could be Chrome breaking audio: https://danshumway.com/blog/chrome-autoplay/ https://danshumway.com/blog/chrome-autoplay/ - It could be Chrome breaking LocalStorage: this discussion - It could be Chrome removing support for a web standard that was implemented and shipped: https://www.chromestatus.com/feature/4642138092470272 https://www.chromestatus.com/feature/4642138092470272 I'm linking Chrome issues here because Chrome is the most visible of all browsers with the largest marketshare, but other browsers have their issues, too.

bzbarsky 7y ago
Just to set the record straight on the part I'm familiar with, "Custom Elements V0" was never a web standard. It was a proposal, which Chrome implemented and shipped without getting everyone else on board, and which turned out to have significant enough problems that a somewhat different thing got standardized and shipped in all browsers ("Custom Elements V1").
- dmitriid 7y ago
  Once something is shipped, people will rely on it. For example, quite famously, Youtube did for a very long time (until this year IIRC). AMP used to use it. There are several polyfills available. Several Polymer versions targeted v0. Etc. etc. It's not specifically Google's fault that they are removing support for these, but, once again, that's the state of the world: browsers are lrage complex platforms that may and will break your app.
  - bzbarsky 7y ago
    Sure. Unshipping things is always hard, and likely to break people. But there's still a difference between unshipping support for a standard and unshipping support for a non-standard technology that only you ever implemented. In the latter case, people should be a lot more wary of depending on the technology in the first place. While it's true that browser updates may break your app, it's also true that there are ways to write the app so as to minimize the risk of such breakage. Using Custom Elements V0 was _not_ a good way to avoid potential breakage...