Without the basic hardware/software ecosystem that android has supported it isn't clear that Firefox OS could (so easily) exist. Modern smartphones have substantially reduced platform openeness and freedom compared to the desktops of old, but the ratchet doesn't only click one way.
But we can't do that, because Firefox OS is clearly inferior to Android in so many significant ways. Its performance appears to be a problem. Its functionality is quite limited. Its "openness" is overstated. It provides an awful environment for developers, in terms of language support, compared to other mobile OSes. Basically nobody is actually using it yet, so there's little incentive to target it. It appears comparatively hostile toward anyone wishing to merely recoup the cost of creating an app, never mind make a profit.
Until Firefox OS gets its act together, it will face criticism and negative comparisons with Android. I hope that people like you are capable of seeing what's truly behind this (that is, the inferiority of Firefox OS compared to Android), rather than misattributing it to "dissonance", or "shilling", or some other nonsensical reason like that.
I'm not misattributing anything and putting words like 'shilling' into my mouth is cheap.
The fact that Android was hailed as open by the community clearly diminishes the impact of the major selling point of Firefox OS.
Even if Firefox OS was on par with Android in all aspects of performance, people would still have no reason to use it, and the argument 'because it's open' is no longer persuasive.
That's very arguably at the very least. As a Ubuntu user at work I can tell you how annoying are all the little bugs, all the drivers issues and hardware incompatibilities.
Yeah, you can tell me that is not linux/open source community fault, but in any case it is preventing to make future software "exponentionally" better.
Other example? I really can't stand GIMP (It is usable but really a good alternative to Photoshop)
1) What laptop are you using? Ever tried building a Hackintosh? Seems to me that either you or your company bought a computer and expected it to just work. In many cases it does so perfectly (for example on my Thinkpad it worked perfectly out of the box), in some cases it doesn't.
2) If you're so annoyed about Ubuntu, why do you keep using it? So you can bitch and moan about it?
A. Use photoshop, and pay the absurd license cost. B. Spend what you would on photoshop to pay some starving GNU developer to implement some features you like from PS in gimp. C. Fix the problems you have with it yourself since it is FOSS and development is open.
This has become pretty apparent with desktop Firefox, for instance. There have been many poorly-thought-out decisions foisted upon its users lately, without them having any say. This has accelerated since Firefox 4 was released. Just look at the one from today about removing the ability to easily disable JavaScript in Firefox 23, for example. I don't see things being any different with Firefox OS, and I don't consider this to be a form of "openness".
The same goes for JavaScript. In practice, it really isn't more "open" than C, or C++, or Java, or Objective-C, or C#. Unless you're part of certain teams at a very small number of organizations, you're not going to have any influence at all on JavaScript. This is very different than the situation with, say, Python, where unaffiliated individuals can actually make a difference.
But I wasn't even referring to standards when it comes to JavaScript. That's peripheral to the lack of choice that exists under Firefox OS. It's not a very "open" platform when the only language you can practically use is JavaScript. Android gives us the option of using Java, or using C and C++ via the NDK, for example. That's far more choice than we have under Firefox OS.
Maybe my comment was harsh, but we are discussing reality here, not some academic fantasy. The evidence just isn't there to back up Firefox OS being more "open", or even practical in any way.
I won't discuss the openness of JavaScript vs. that of other languages, since this doesn't seem to be the purpose of your message. Yes, JavaScript is the only way to get code executed on FirefoxOS. However, considerable steps are being taken by both Mozilla and third-parties to ensure that this does not limit (too much) your choices. These days, dozens of languages can be compiled to JavaScript, directly [1] or indirectly [2], including C, C++, Objective-C, Java, C# or Python. That doesn't mean that all your applications can be ported immediately to FirefoxOS, as you'll need some library support that may or may not be available for the platform, but it's hardly limiting.
As for your "academic fantasy" paragraph, well, let's just politely ignore that trollbait.
Caveat: I'm a Mozillian.
[1] https://github.com/jashkenas/coffee-script/wiki/List-of-lang... [2] https://github.com/kripken/emscripten/wiki
You couldn't be more wrong. Firefox OS is developed in the open, on GitHub. You can submit pull requests. Others have. They've been accepted. FFOS is implementing a very cool text selection concept that came from the community, for example.
Android is developed behind close doors. Only release versions are opened sourced. Android does not accept patches from non-Google employees.
> Android gives us the option of using Java, or using C and C++ via the NDK, for example. That's far more choice than we have under Firefox OS.
On FF you have the option of using any language that compiles to JavaScript, which has all of the same API capabilities as JS. This is not true on Android, where every attempt to port a JVM language to Davlik has failed (thus far).
I base this on statements made in the #android IRC channel in the past by Google developers working on Android.
As for FirefoxOS, is it possible for a user to install XPIs or XPCOM components on their own handset? I can understand why limitations would be placed on third-party applications obtained through a web service, but not why owners of devices could not install additional components.
I confirm that Mozilla has fixed a number of bugs and/or performance issues in Android. In fact, if my memory serves, Chrome for Android simply couldn't load without our patches :)
However, if my memory serves, getting these patches accepted has proved pretty difficult. I'm not the author of the patches, so I couldn't tell you why.
> As for FirefoxOS, is it possible for a user to install XPIs or XPCOM components on their own handset? I can understand why limitations would be placed on third-party applications obtained through a web service, but not why owners of devices could not install additional components.
Well, given that XPCOM components have 100% access to the file system, hardware, etc. and can easily brick a phone, we didn't really spend time making that footgun user-friendly. So you can easily add an XPCOM component, but only if you build an image of FirefoxOS yourself. Not too hard to do, just probably not the answer you hoped for.
A platform being open is not merely academic. It makes future open source software exponentionally better just like it did in the past decades. In fact, if this gets mainstream it will be the first to be truly open. Android has an open source license, but Google has never been really open about it. http://www.itwire.com/opinion-and-analysis/open-sauce/55247-...
And why does relying on a publicly specified language with vibrant ecosystem make the platform less open? You argued that by using proprietary languages? Though I completely agree JS needs to mature... a lot.
I trust Mozilla's vision that they're doing the right thing to move the web forward by putting efforts into desktop or mobile or whatever they find worthwhile.