This is all good but it's also a chicken and egg problem.
The lack of web push notifications for one of the two major mobile platforms will prevent that feature from being used + any adjacent features that would be used in more viable web apps.
In my opinion, nearly all good-guy arguments for Apple in this debate are negated by them not implementing that single feature. It is not new, obviously useful, obviously not a privacy concern and obviously blocked because it might impact their app store revenue.
I want Apple in this game implementing this stuff in a privacy concious way, rather than saying lol no make native apps and ceding the web to Google.
My argument isn't really a "good guy" Apple argument but more of an observation of the current kidnapped state of the web RFC's.
I usually adopt latest pretty quickly since I can afford ignoring Safari.
e.g. When createObjectUrl was a new thing. I ended up doing something using AJAX and doing some processing server side for IE and Edge. Now I could have done all the processing server-side. However 80%+ of the users use Chrome. So instead of checking everything on the server, I could offload 80% of that to the browser.
There is a tooling out there to assist you and most of the compatibility issues are well documented now. 10 or so years ago when I started that really wasn't the case.
Some Google engineer’s promotion case.
It can't even be 1% of websites out there embracing this stuff. I'm guessing the biggest consumer for most of the new features in Chrome is probably Google web developers. There's quite a lot of things that only end up half implemented, too.
Although the RFC these days seems to just be a design spec doc for Google, I suspect you could carve it down to less than half of what it is and render 99.9% of websites out there just fine.