zlacker

There is one good reason. The web is a large ecosystem, and we're all living in it. You have a right to express your opinion about its development, and as a responsible inhabitant of that ecosystem, you should exercise that right.

Or, in other words, since we live in it, if the web turns into shit (even more than it already has), we'll have to live in that shit.

>>TeMPOr+(OP)
I said they couldn't express their opinion? No - I even validated it by saying "sometimes I feel like that, too" and prescribed a simple remedy that would cure the problem: turn off JS.

My opinion, since we're expressing them as responsible inhabitants of the Web, is that bringing the web to feature parity with mobile apps - in a responsible and well-governed way as I believe the standards committees who worked on the ServiceWorker spec have done - does more to keep it relevant and provide good User Experiences than forcing devs to try to match user expectations without the facilities.

Since we're expressing opinions, here's another one: Apple is purposefully dragging their feet by not implementing these things fully on Safari because they want to protect their precious walled garden as long as they can to the detriment of everyone else using the web.

Back to the original point I made - if you are concerned about the things being bolted on to the web "turning it to shit" you can turn them off. Maybe the UA vendors should make that easier to do, or easier to do selectively? That's an opinion you could express to them.