The article itself cites things like the lack of support for WebRTC and Service Workers.

Service workers seems like a performance and battery nightmare.

I can't find a single iOS app I use that needs either of these.

I'm not sure if you're trolling or sincere here. Of course iOS apps don't need them, they are native. We are talking about the capabilities of the iOS Safari browser.

That's my point. I'm rarely, if ever, in my browser on either of my iOS devices (iPhone 6 or iPad).

If you're not writing a native app, don't bother. Facebook learned this lesson, I'm sure everyone else does eventually as well.

Yeah, because the browser doesn't offer the capabilities needed to render native apps redundant. I'm not sure why we're talking in a giant circle here.

Clearly, the "build for IE6 + Windows" of 2016 is "build for native iOS", which was the original point I was making.

iOS apps are written in languages that have the ability to do equivalent things.

You learn to evaluate technologies working in a relevant sector or studying some information systems stuff. No citation needed IMHO.

Would you demand citation if I tell you that 'mov ax, data' in assembler moves data to ax or look it up if you don't trust your own judgement at the moment?

They'd probably ask whether we're working with AT&T- or Intel-style syntax ;)