There is a difference between "self determination" and "referendum performed under armed guard, with no international election observers allowed into the country", but it's a subtle one, I grant. That said, it's the sort of difference that can give you a 95% "Join Russia" vote, with 80% turnout (76% of total voters, if you do the math) in a region where at most 60% of the population is ethnic Russian and at least 10% (the Tatars) are _extremely_ unlikely to have vote for union with Russia.

If you think those referendum results are fair and represent self-determination, I have a bridge I'd like to sell you.

You need an account if you want to use Mozilla's sync service.

If you don't want to use sync, or if you want to run your own sync server instead of using Mozilla's, then you don't need an account.

Uh... They do have gas. In Crimea. See http://www.reuters.com/article...

Assuming the extension works on Chrome on iOS. Which it may not, since that uses a fairly different architecture and rendering engine from Chrome on other platforms...

For what it's worth, "millions of dollars" is a pretty low bar. A million dollars in the US will get you _maybe_ 5 person-years worth of work from anyone at all competent (using the normal rule of thumb that an employees cost to the employer is about 2x salary once you take into account benefits, employer taxes, equipment, office space, etc).

So 10 million dollars will get you a 10 years worth of work from 5 developers. As an example, the PyPy project is 10 years old....

For JS, between the various browser vendors, the right number is probably closer to 300-500 person-years (see https://news.ycombinator.com/i... for an attempted breakdown). Figure $100 million as a low estimate. Chances are, the people involved are being paid more than $100k a year, so adjust the estimate up accordingly...

1. All addons hosted by Mozilla get reviewed.
2. Open source is not required, but source disclosure to Mozilla is.
3. Any update to the addon triggers a new review cycle.

The other option is to review updates to extensions before pushing them out to users. That's what Mozilla does with Firefox extensions.

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...