This seems like the worst possible outcome:
> Why do all browsers have to support the same standards? This only limits their innovation, and limits web developers.
Shouldn't the solution instead be a new, more powerful standard? (Ignoring how pie-in-the-sky this is.) As in, not band-aids like AJAX and Flash, but a from-the-ground-up standard? After all, 99% of iPad apps have the same basic capabilities; there's no reason you couldn't have a standard which replaces HTML which could fully cover those apps. Then, if you have a need for a really specialized service, you can create a dedicated app.
Standards are for lowest common denominator and almost by design are never, ever simple enough - see e.g. SOAP vs REST, XML vs JSON (Dave Winer be damned).
 Notwithstanding: http://news.ycombinator.com/item?id=1304244
XML and SOAP came out of "let's invent new formats and protocols"-type standardization, while REST and JSON were products of (essentially) one guy looking at a simple, existing, well-known concept (HTTP and js object literals, respectively) and putting a new frame around it.