I focused on some APIs I know about. There's nothing strawman about facts that you misrepresented in your diatribe. How can I be sure that you represented everything else correctly?
Oh. I can't. Because I also saw your section on "Edge differentiation".
Should I go through everyting else and discover same misrepresentation and falseness? I think I won't, these two are quite enough, thank you.
> Instead let’s focus on the core issues
You keep skipping from goal post to goal post, and each next argument you make isn't made in good faith.
> 1. 2.
I'm not even going to dignify this speculation with an answer
> 3. 4.
And again and again all comes down to literally one or two standards. That's it. That's all you really have.
Well, sometimes you have more, but then it's just a random dump of random standards that you are absolutely sure are actual standards (and not "Draft comunity reports" by Google) and that everyone must implement them now.
> Without a viable web ecosystem on iOS mobile
Please define a "viable web ecosystem". So far it looks like to you "a viable ecosystem" is "anything that Google implements, others be damned".
> web apps are dead
Yes, they are dead. For many reasons that have nothing to do with notifications.
> The fix for this scenario is competition. With a 60% market share on MacOS
Yes. Let's talk about competition. There is none, it's fully dominated by Google: https://news.ycombinator.com/item?id=31905404
Oh wait. You don't really care about that.
> A highly funded Webkit be able to contribute to the web ecosystem instead of holding it back.
Webkit is contributing to the web ecosystem, and isn't holding it back. For the obvious reason that your definition of a viable web is taken straight out of Google propaganda, and has nothing to do with making the web viable.