Complaints about HTML/Web apps not feeling "native" is a canard. Hundreds of millions of people use web pages every single day, from the most technical neckbeards to the least technical AOL grandmas. Now non-technical users probably aren't spending much time on sites with bullshit user experiences but there's a mind boggling number of websites people use daily. Native apps are also rarely bastions of usability and paragons of user experience virtue. Web apps don't need to "feel native" because the appeal of "native" apps doesn't really exist in the minds of actual users. These hundreds of millions of users aren't being held back from anything because they're using web pages instead of native apps.
Users want services and content and they're happy to access them through a web browser. In fact a web browser makes it easier for them in most cases because they don't need any special software before they access said content and services. Whatever device they're using likely has a web browser accessible. If they see a URL they can pop open their laptop or pull out their phone and access it immediately.
When they're on their phone they don't want it to take forever to load when they're stuck in a slow 3G area with no WiFi. They want it to work on the iPhone they just bought as well as their Windows PC back home. If they buy a Mac for their kids they want it to work on that as well.
The major features HTML5 added were ones that help web pages not feel more like native apps but have better interaction with clients. Clients aren't as limited as they were in the past (I remember a time before the <img> tag) and a richer DOM is important for the increased amount of work (Javascript, CSS, etc) being done on the client side.
These people complaining about performance on mobiles is just jackassery. The mobile web experience had the same sort of constraints that native mobile applications have. Mobiles have tiny batteries, often have small screens, are controlled with fingertips rather than mice, and often have slow high latency internet connections. Again it goes back to graceful degradation that users are already expecting. Maybe the mobile version doesn't load the 2MB PNG background and the uncompressed 1MB Javascript from a totally different server (requiring a second set of DNS lookups) out of which you only used two functions. The mobile native app wouldn't have the 1024x1024 icons or the 50MB 1080p intro movie bundled with it either.
HTML5 doesn't need to bring a more desktop-like experience to mobiles. It also doesn't need to make apps that look native. It needs to be used to make web apps functional and do their business with the least cognitive load on users as possible. It should scale well no matter how large the screen is or how shitty the connection speed. Instead of all singing all dancing bullshit I'd much rather see a page load on my phone and then let my fucking CPU go to sleep so I don't waste my battery trying to read a tweet or a Facebook message.