4 ms·
> Even Mozilla is going down this route with their browser apps. Why are you saying that? What Mozilla is doing is to develop web APIs needed for those apps a
by bad_user 12y ago
> Even Mozilla is going down this route with their browser apps.
Why are you saying that?
What Mozilla is doing is to develop web APIs needed for those apps and then push for their standardization, but all the apps listed in the Firefox Marketplace are just web apps, having no problem in running in other browsers (assuming they don't rely on APIs that haven't been standardized yet). Google is also doing this with Chrome on Android, as they've also been pushing for certain standards to be adopted that would benefit apps.
Of course, I also worry about ARC or NaCL or Dart (what's with Google these days?), however the work that Mozilla and Google are doing on those web APIs meant for apps is really not the same thing.
- whoisthemachine 12y ago> Of course, I also worry about ARC or NaCL or Dart (what's with Google these days?) That's fairly typical of Google to have 2 or more of everything. Inbox and Gmail, Chromebooks and Android are prime examples. Ars Technica has a write-up on it that lists more: http://arstechnica.com/business/2014/10/googles-product-strategy-make-two-of-everything/ http://arstechnica.com/business/2014/10/googles-product-stra...
- comex 12y agoJust for the record, ARC is a runtime you statically link to in your NaCl app (not an alternative core Chrome feature).
- whoisthemachine 12y agoHuh that's interesting. I haven't looked much into ARC (or NaCL for that matter), I just wanted to point out to the parent that it's fairly typical for Google to go down multiple paths for a specific market need. They're kind of the anti-Apple in that regard.
- bliti 12y agoGood points. My worries are more directed towards the browser becoming a second OS and moving towards client apps. I guess I'm old school and am still tied to good old html.