I know that. But your comment was like answering a question about optimizing a Python snippet with a recommendation to use C++. If you don't like hybrid apps (or Python, or whatever), that's fine, but it doesn't mean that bringing it up aids the discussion. Trust the developer to understand the tradeoffs of their tools and stack.

My point is that native applications are the only way to take proper advantage of the hardware.

You cannot try to bend something thought to display documents into some kind of application, and they complain about lack of hardware acceleration.

Why not have a document with hardware accelerated effects? Anyway, we're talking about a feature which already existed and worked quite well, which Apple felt the need to discourage the use of, probably for battery reasons. Which is fine, but it's annoying that they didn't document it in more detail.

It's ultimately the developer's responsibility to make good choices on behalf of users, whether on native, hybrid, or the mobile web.