4 ms·
Sorry but it is completely your own fault. We've been using Service Workers on production for two years now, and never had any issues of any sorts. Also kudos f
by lazysheepherd 8y ago
Sorry but it is completely your own fault. We've been using Service Workers on production for two years now, and never had any issues of any sorts. Also kudos for "trying" a new API on production.
- icebraining 8y agoPlease consider the guidelines: When disagreeing, please reply to the argument instead of calling names. "That is idiotic; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3."
- alluro2 8y agoPerson 1: "It didn't work for my single use case / environment / circumstances = non-working garbage" Person 2: "It worked for my single use case / environment / circumstances = the best thing ever, it's your fault" :)
- dekhn 8y agoI'm a software engineer who works for Google who has worked on web tech for 25 years (hello NCSA and CERN). We went into this because a web dev on the team thought it would be a good solution, and put a bunch of work into it. After some time, we noticed that it added a ton of complexity and violated many of our core assumptions about how web pages work. Note that service workers weren't really new when we used them, we deployed them carefully and with intent, with skilled developers. Don't get me wrong- I like the idea behind service workers- I just found how they were implemented to be difficult.