Apple sees App Store apps, and web apps as having different advantages, and it is in their interest to have the best platform for both.
It’s not just me saying this, they keep saying it too, and proving it by investing in making web apps run better.
Believe whatever you like.
But this means you are also choosing to ignore absolutely enormous investments at every level of the stack that they have made to increase web performance, adopt standards and improve web user experience.
Disclosure: I work at Google on JS libraries, and at one point was in the Chrome org, but my opinions are my own.
You'll probably know better than me but Apple's work on Webkit was presumably worthwhile enough for Google to fork it into Blink (no problem with that but maybe worth acknowledging that fact).
Google forked Blink because for whatever reason they were unsatisfied with the state of Webkit -- nominally because they wanted to take a different approach to multi-process, but there may have been other technological and project direction/pace disagreements. Since then, a number of browsers have switched from Webkit to Blink/Chromium as their engine, and arguably Safari is falling behind on new features and overall quality (weird quirks that require web devs to work around).
If Apple's focus is on getting better power consumption and memory use (esp on mobile) then that's still investing and arguably that does as much if not more for users and the web than adding more features.
PS Let's not forget that Apple are still standing behind WebKit when Microsoft have given up on their own rendering engine so let's give them some credit for helping to avoid a Chrome only web.
It’s hardly obvious that this is best for users in the long run.
I point this out not to say it’s wrong for them to attempt this, but because it makes no sense to use Google’s strategic decisions as evidence of Apple’s intentions or investment.
The method to pin a webapp to the home screen is substantially worse than it used to be.
There was a period where javascript running in Safari ran significantly faster than javascript running in a webapp opened from the home screen, or in any other app opening a web view. Is that still the case, or did they decide to share that function?