This document reads like an enumerated list of why the web is better than apps for most things. Unfortunately, apps will likely prevail until OS producers work directly to empower the mobile web.
And, frankly, I would hope that in general that apps win. Not the kinds of apps that are just a wrapper for a website necessarily, but for a great many things I'd prefer an app running on my hardware in a way that I can control with things like a firewall to some sort of cloud solution that I'm accessing through a browser.
Windows Phone 8.1 & Windows RT 8.1?
They do have similar, perhaps not quite as bad guidelines. However most don't complain because iOS is way more popular as a target.
It also contains a severe condescending tone how 'big daddy' is doing all this for our own well being. And of course, think of all the children!
That being said, the approaches we're exploring with famo.us (a retain-mode scene graph) is absolutely essential for allowing web apps to compete with native apps. This approach is often overlooked by web developers who grew up on the web and are not familiar with how native windowing and retain-mode UI systems function.
So you want web apps that are not web apps (with special hooks to the hardware and native features etc).
Having your cake and eating it too in other words.
Is that an unreasonable thing to expect? HTML touch events are provided by a special hook to the hardware and/or OS. The same applies to audio/video elements, WebGL, geolocation, websockets, and any number of other APIs. That's just how the web platform has been developing, and there's no reason to think it will stop.
If someone could replicate those on an app layer that wasn't the DOM and javascript, so you could simply link to a URL and download and run an app with high performance I reckon we could stop abusing the web.
Still a pretty tall order though.