Apple doesn't have to take web apps into consideration when they're considering changing the platform or the API however they see fit. They're committed to upho

Apple doesn't have to take web apps into consideration when they're considering changing the platform or the API however they see fit. They're committed to upholding open web standards, but have no similar commitment to their own API. HTML standards are slow to evolve by design, and Apple is okay with that, however that is the last thing they want with their own software stack. Apple isn't focused on developing a smart phone operating system. They're focused on redefining what a computer IS, and how we interact with them. That's why they've been so careful about copy+paste, and later multi-tasking. They are taking this as a chance for a clean slate approach to computing and don't want to be hampered (or their customers to be hampered) by slow-moving third party compatibility layers. How much as Window's development hampered by the fear to break legacy apps compatibility moving forward? Apple isn't afraid to make their developers jump through hoops and make changes if they think it will benefit the platform in the end (a la the Intel switch). They'll provide tools to make that as painless as possible when the time comes (e.x. iPhone app compatibility on the iPad, Rosetta) but having another layer in between only slows this process down. Whether you view Apple's actions as that momentous and revolutionary is largely irrelevant. I think THEY do. Not that I'm not upset by this as well, but I'm trying to make sense of it.