4 ms·
Also: https://wiki.mozilla.org/B2G https://wiki.mozilla.org/B2G My first reaction: Great, I'll look again in 2 years when something like this can reasonably be
by MatthewPhillips 15y ago
Also: https://wiki.mozilla.org/B2G https://wiki.mozilla.org/B2G
My first reaction: Great, I'll look again in 2 years when something like this can reasonably be ready. In the meantime I hope the Chrome Phone rumors are true.
My second reaction: So they're going to use Android which brings a lot of non-web baggage that they'll have to strip out. The plus side is that it might mean they can push something out in a year or less.
EDIT: They're not using the Android Java APIs[1] so they will have to rewrite the browser layer, they can't reuse the Firefox Android app. Using Android just for the drivers is a good decision, without a doubt, but this is going to take a while.
[1]https://groups.google.com/forum/#!msg/mozilla.dev.platform/dmip1GpD5II/KYD4ejBMZJMJ https://groups.google.com/forum/#!msg/mozilla.dev.platform/d...
- shaver 15y agoFirefox on Android uses very little in the way of the Java APIs, it's virtually all NDK code. That said, it will certainly require some meaningful adaptation.
- rpearl 15y agoMy understanding is that the kernel will be based on Android. Userland code will be rewritten basically entirely, to boot to a gecko-based UI.
- bergie 15y agoUsing Android just for the kernel sounds strange. MeeGo would be the distro actually designed to be used with your own UX layer (in this case, the browser engine)