7 ms·
Boot to Gecko: building a complete, standalone operating system for the open web
- RexRollman 15y agoSo they are going to reimplement ChromeOS with Gecko? Or are we talking about something else?
- MatthewPhillips 15y agoLooks like they are going to fork Android and have it boot straight to Firefox[1]. EDIT: Correction, they're using Android for the drivers only.[2] It will not boot to the java APIs, so it won't be the Android Firefox app. [1] https://market.android.com/details?id=org.mozilla.firefox https://market.android.com/details?id=org.mozilla.firefox [2]https://groups.google.com/forum/#!msg/mozilla.dev.platform/dmip1GpD5II/KYD4ejBMZJMJ https://groups.google.com/forum/#!msg/mozilla.dev.platform/d...
- tedmielczarek 15y agoThe "Android Firefox app" is just Gecko, a bunch of C++ code rendering to an Android widget. That's like calling the Windows version the "Windows Firefox app".
- shaver 15y agoThis is a FAQ; I should finish writing the FAQ, clearly. We’re currently aiming at mobile/tablet devices rather than a notebook form factor. We’re looking to expose all device capabilities such that infrastructure like phone dialers can be built with Web APIs, and not only “high level” apps like word processors and presentation software. We also want to provide a stack that's open down as far as we can, and not just the browser-like top layer.
- MatthewPhillips 15y agoAlso: 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)
- devongovett 15y agoThis is a complete waste of time and development effort in my opinion. Why would anyone ever want an OS that does nothing but show a web browser? Don't get me wrong, I love web apps and build them myself, but isn't the point of web applications to be fundamentally cross platform? Also, the web platform isn't ready to be the only platform available for applications. I have yet to see a decent web based word processor, something that most users will want to use. The formatting options available in the web based word processors that I've seen have been very limited, and pale in comparison to even Pages on the iPad. In summary, the web platform isn't ready for all types of applications yet and because of that combined with the fact that people looking for cheap and simple computers aren't even buying traditional hardware anymore - they're buying tablets. So, Mozilla, why waste your time with this project and instead use those development resources to make Firefox and the web platform better on all of the existing operating systems. Let Chrome OS see whether anyone actually wants something a browser OS.
- shaver 15y ago"Also, the web platform isn't ready to be the only platform available for applications." That's the whole point. The web wasn't quite ready to subsume PDF, until people went and tried to do it, found the pieces that were missing, and got them added. We expect and hope that we're going to hit a ton of things that don't work today, and that we'll have to make them work and get a standardized API and so forth. I think that's a better way to proceed than to make speculative sky-APIs on standards mailing lists. We are exactly targetting mobile devices (handsets and tablets), because we agree with your assessment of where things are headed, and because that's where the app action mostly is today. (We want to solve the app-store-for-web problem too, but that's another project.) This isn't just about the web apps you have today. It's about having your contacts manager, camera, gallery, dialer, SMS app, GPS-integrated maps, launcher etc. be hackable using web tech. That work will help on desktop as well, since many of those pieces are on desktop/laptop machines -- if you write OS-specific code to get to them, and you're allowed by the OS to interpose your version of it. Maybe you're right, maybe it's a fool's errand. We think it will help the web grow in powerful ways, and make important internet technology be accessible to more user-focused customization, so we're going to try it. That's basically what we do.
- dreamdu5t 15y agoRemember: Mozilla was the first major browser to offer cross-OS support for Windows, Linux, and MacOS — as free software no less. They're looking to the future, not what is possible but what should or could be possible. I'd much rather have Mozilla working on an "OS for the web" than Google, despite whatever problems Mozilla may have.
- sayhello 15y agoI'm curious, what problems do they have?
- rkwz 15y agoFunding.
- rpearl 15y ago[Citation needed]
- rkwz 15y ago>>I'd much rather have Mozilla working on an "OS for the web" than Google, despite whatever problems Mozilla may have. In this context, one of the problems that Mozilla has compared to Google is money.
- deleted 15y ago[deleted]
- dreamdu5t 15y agoThey've got 100 million. That's enough to do amazing things. Honestly, for all the money Google has, Google+ isn't very impressive. Interestingly, about half of that 100 million comes from Google to secure their spot as the homepage and default search.
- 15y ago
- Astrohacker 15y agoWe are clearly moving towards a world of more web-based applications, but I'm disturbed by this because it means all my data is stored unencrypted on other people's computers. We're slowly placing our lives in the hands of the essentially anonymous individuals who control the apps we use. Here's an alternative that we could in principle choose: Apps can be delivered over the web, but data is stored locally. If it is backed up remotely, then it is encrypted first. If our app communicates with other users, then it does so P2P instead of through a central service. These steps would ensure the company whose app we use only knows that we are using the app, and not what our data is or who else we are interacting with. Unfortunately, this technology is not very easy with the present state of JS/HTML. I'm not even sure if it is in principle possible for a JS app to create a TCP server. Some quick Googling reveals it may only be possible if you use Flash.
- dangoor 15y agoActually, getting the code from the server (and caching it) and storing data locally is already a solved problem. Take a look at IndexedDB, which is already supported by Firefox 4. The idea here is to think of apps as being built on web technologies but don't think of them as being delivered like and acting entirely like today's most common webapps. Beyond B2G, Mozilla is exploring what it means to be a "web technology-based app" and interesting things are already coming of the project and even more interesting things are yet to come. https://apps.mozillalabs.com/ https://apps.mozillalabs.com/
- rkwz 15y ago>>Apps can be delivered over the web, but data is stored locally. If it is backed up remotely, then it is encrypted first. If our app communicates with other users, then it does so P2P instead of through a central service. I really wish this to happen. But unfortunately your next statement, These steps would ensure the company whose app we use only knows that we are using the app, and not what our data is or who else we are interacting with. clearly says why it wont happen.
- dave1010uk 15y agoWhat you're describing is very similar to W3C's Widgets: http://www.w3.org/TR/widgets/ http://www.w3.org/TR/widgets/ Widgets are zipped up HTML/CSS/JS files so can easily be emailed / bluetoothed between phones. Communicating with other users is a bit harder but HTML5 Device APIs should provide what we need in time.
- dave1010uk 15y agoThe "new web APIs" look like the W3C's Device APIs: http://www.w3.org/TR/dap-api-reqs/ http://www.w3.org/TR/dap-api-reqs/ Are Mozilla working with the W3C or doing their own thing?
- tedmielczarek 15y agoThere are people at Mozilla following and interacting with the Device APIs WG, as with most W3C standards groups, but there will also probably be some measure of invention, as standards groups are a poor place to invent. Historically Mozilla has both implemented standards as well as shipped prototype implementations to test ideas that have not yet been standardized.