> Mozilla wants to use the web as that platform exclusively, which is fine if everybody is already making everything for the web and there is nothing of importance you can do with native code that you can't do from the web. But neither of those is true so their strategy fails.
There are things you can do on iOS that you can't do on Android (e.g. Apple Pay), and vice versa (e.g. Google Now). iOS fails the "there is nothing of importance you can do on Android that you can't do on iOS" test, and Android fails the "there is nothing of importance you can do on iOS that you can't do on Android" test. Yet here we are, with two successful platforms.
I think the truth is a lot more nuanced, and in particular I think the emphasis on "native code" is a convenient red herring. (Android isn't really native code for anything but games, and iOS Objective-C is technically native code, but that Smalltalky object system is not up to C++-level performance, so the distinction doesn't mean much.)
