Agreed. I also found this amusing: "What is a simple task on native apps can be a decidedly more complex and time consuming task with HTML5." While this is true for some tasks (web audio still sucks), it's the other way around for other tasks (last time I tried to dynamically re-flow text in iOS was a nightmare).
They also assume a gaming context, which is just one of many things that can be done with HTML5. The way I see it, HTML5 is absolute ready for use, but not fully matured, similar to web applications in the days of Netscape. Understand the tradeoffs of the various ecosystems, and pick the best tool for the job.
When I want to dynamically re-flow text on iOS, I use HTML in a UIWebView. Otherwise, native is easier for presenting a navigable and interactive UI. Using the right tool for the job is always the way to go.
They also assume a gaming context, which is just one of many things that can be done with HTML5. The way I see it, HTML5 is absolute ready for use, but not fully matured, similar to web applications in the days of Netscape. Understand the tradeoffs of the various ecosystems, and pick the best tool for the job.