Because most of the packages that do something useful involve interaction with the OS.

Sandboxing the python runtime, say, means breaking most of the packages python developers take for granted, no?

It depends.

Once you're in steady state, and if you don't use workers and don't use the new parallel processing primitives people are proposing for JS, you're right.

But during JIT warmup, and any time you have to JIT a new function or new codepath it matters because on multicore hardware you can do background compilation.

Mozilla fully supports single-line flexbox (that is, flexbox in which the child flex items are all layed out in a single row or column), which is what most flexbox use cases want, and has for a while.

What's missing is support for multiline flexbox.

As far as I know, in Colombia, Venezuela, Spain, Poland, so far.

FirefoxOS performs a lot better on devices at that price point than Android does.

The target audience is people who don't have a smartphone yet, most probably because they can't afford to pay for a $500 phone. Which is most people in the world, so far.

Are you in a market where it's available in stores? The marketing has mostly focused on those markets, obviously.

That said, the launch was covered on Slashdot back in July: http://mobile.slashdot.org/story/13/07/09/1414232/mozilla-launches-firefox-os-devices-in-stores-opens-up-app-payments and several other articles, as well as other tech press. No non-tech-focused marketing in the US so far, since it's not like you can buy one of these in a store in the US right now...

Noise reduction is great. And airlines have no problem with you wearing headphones, except during takeoff and landing. Every single airline I've ever dealt with will ask you to remove headphones then, to make sue you can in fact hear announcements.

This has nothing to do with electronics and everything to do with them needing you to be able to hear directions clearly in an emergency.

Actually, WebKit cuts corners on standards a lot more than Firefox and IE do. For example, the official CSS 2.1 test suite from when the standard was finalized two years ago shows WebKit passing about 89% of the tests (for comparison, Firefox passed about 97%).

If Firefox/IE aren't rendering a page and WebKit is, it's almost always because the page author has written WebKit-specific code (e.g. used -webkit CSS prefixes on properties that are supported without a prefix in other browsers).

What WebKit and especially Chrome _does_ have is much better marketing. Not least because they have a much larger marketing budget than, say, Mozilla. Sadly, their marketing is working well on you.

Firefox doesn't use keychain access on Mac. It uses its own password store, encrypted with its own master password. That's why https://bugzilla.mozilla.org/show_bug.cgi?id=106400 is still open.

Likewise on Windows, last I checked.

I haven't checked recently whether Firefox use gnome-keyring on Gnome, but based on past code inspection I rather doubt it.

Fwiw Costco's numbers are about $11.50/hr starting and $20/hr average. So somewhat better than Apple.

But Apple is still way better than other retailers...

Airline pilots are typically paid an hourly rate, but only for flight hours. It's pretty messed up.