> We already have HTML5 for that, why would we need yet another method for the same thing?
Aspects of this are limited for security reasons. Changing the location of the application, to treat it as something different, allows for different levels of security.
> Again... this is all possible with HTML5.
Again, to a limited degree for security reasons.
> Show me a recent native app that has the success rate of Facebook or Twitter.
Just look to Apple's App store as a good example. Look at all the native Twitter apps that people used over the web interface.
> A lot of native apps are just interfaces to web apps.
Yes, and why do you think that is? Because being treated as native apps gives them additional flexibility. With browsers able to "install" web apps, they can provide additional functionality to these applications that otherwise couldn't exist.
> With bookmarking them and making the app use HTML5 app cache.
Yes. So at least your aware that what Mozilla is doing isn't new. Apple's done this. Google's done this. Mozilla is following.
Couple this with other benefits:
1. Having a trusted app store where you can get your apps.
2. Allow for an easy system to setup and sell your app. Envato does this. Apple does this. MS is planning on doing this. Google does this. You also make the assumption that developers can easily accept payments. It's not that easy, unless you bow to the will of PayPal.
3. Mozilla not doing this would leave it behind. Suddenly, if people wanted to use these web apps, they'd have to switch off Firefox.
I've presented many reasons why this is a good thing. You've questioned everything, but offered little in the way of why it's bad. Might you care to offer up reasons why this shouldn't happen?
> Ohhh and let's not forget the "native" applications that in reality wrapped web apps.
Huh? Native apps that are just connect to web API's are still native apps.
We already have HTML5 for that, why would we need yet another method for the same thing?
> 2. Snappier applications, since everything is stored locally.
Again... this is all possible with HTML5.
> 3. You'll still be capable of being connected remotely. 4. Ability to use the app even if you aren't connected, or cannot connect remotely.
...HTML5 or Google Gears maybe.
> Also, you assert that we were moving away from desktop apps, when the opposite is true.
Show me a recent native app that has the success rate of Facebook or Twitter. A lot of native apps are just interfaces to web apps.
> Even on an iOS device, you can run web apps as if they are local applications.
With bookmarking them and making the app use HTML5 app cache.
> Being able to install an application on your phone outside the App Store.
install = bookmark
Ohhh and let's not forget the "native" applications that in reality wrapped web apps.