Note that Alon Zakai, who published this demo, is also the person who wrote the Emscripten LLVM-to-JavaScript compiler. So I think he does deserve a cookie. :)

I'm back here because Reddit is down too.

Comment system is not bad.

Stories are good. ...but there just aren't very many of them!

This is a feature we want to add, but we haven't got it yet. Until then, you can try the Bigger Text add-on, which adds simple font size controls instead.

The Android version uses the Android NDK to run Firefox's existing C and C++ code. A pure Java version would require rewriting all of that code in Java, which is a much harder task.

This article explains why the beta uses so much storage, and how we're making it smaller and faster in the next release.

See bug 591661 where this is reported - one of the comments has a (slightly annoying) workaround to use your own sync server in Fennec.

There's a bug that causes random system freezes on the original Droid and the Droid 2: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fbugzilla.mozilla.org%2Fshow_bug.cgi%3Fid%3D602252 Unfortunately we just discovered this today, too late to fix it for beta 1. We'll fix it before the stable release, of course.

The beta release requires a newer processor than the Hero. See the system requirements page for details, and an experimental (non-optimized) build for older and low-end phones.

Note: I am on the Mobile Firefox development team.

Load time is definitely an issue on Maemo. The built-in MicroB browser uses "faststart" which means that it starts a process when the device starts up, and that process stays in memory even after you close the browser. Firefox 1.1 doesn't use faststart, but we and Nokia are working on it for version 2 which will be the default MeeGo browser.

The "fennec" process running after you close the window is a bug, and one that I don't think we've seen before. If you'd like to help us solve it, you can report it here or to bugzilla.mozilla.org. Thanks!

Note: I am on the FIrefox Mobile development team.

MeeGo for Handsets is actually based heavily on Maemo. From our point of view at least, it's an incremental change rather than a complete replacement. Firefox for MeeGo will be an evolution of Firefox for Maemo. Of course, it helps that the bulk of Firefox code is already platform- and toolkit-agnostic - for example, we already have Qt builds for Maemo 5.

The thing is, most people with a Nokia phone never install a 3rd-party app.

It's real Java. You can use most existing Java libraries. What's different is:

* It uses its own bytecode and its own virtual machine instead of the JVM.
* It uses its own GUI libraries rather than AWT or Swing.

So, you basically need to write your UI from scratch - but otherwise you can reuse any existing Java libraries and source code.

Applications can store all of their data files and resources on your SD card. Many do already. It's just the executable code that has to be installed locally.

Back when Apple's aquisition of NeXT was first announced, Apple had indicated that they'd continue to support OPENSTEP Enterprise (the Windows implementation of OpenStep). But it was killed off pretty quick.

You can swap arms if you're very careful, but if you don't do it just right they can break. The LEGO company doesn't consider them removable.