I agree regarding the relative quality, but developer tools have no place in a default Firefox install; the whole point of Firefox was to streamline Mozilla by moving as much as possible to plugins. It's unfortunate that they've recently started bundling stuff again (developer tools, PDF reader, pocket (whatever that is), etc.).
> Chrome's underpinnings V8 and Webkit found new uses outside of Chrome
To be clear, WebKit came from Apple (as a fork of KDE's KHTML), so this wasn't really due to Chrome devs; they were just part of the WebKit bandwagon.
Gecko (Firefox's rendering engine) was already quite widespread before Chrome existed, e.g. it was/is used in Gnome and GTK programs (Epiphany for sure, and I assume other HTML-consuming applications like Liferea); similar to the way KHTML is used in KDE programs, although it was more painful to integrate. Some of these programs were cross platform, so may have had a reasonable userbase (I don't know; I've used Linux exclusively for about 15 years).
Programs based on the XUL toolkit presumably had a much larger installed base; e.g. Thunderbird, RSSOwl, Songbird, Miro, etc.
> Furthermore, Firefox was late to Android
Well, Chrome and Android are both Google projects; we could say that Chrome was late to FirefoxOS ;)
> Part of the problem is a website/webapp developed and debugged using Chrome will work with Firefox more often than not
This is tricky; when I was doing Web dev around that time, I'd do a quick checking in FF or Chrome (whichever I had open) to spot glaring problems, then switch to IE6 for my serious testing.
Completely agree! But the fact is, Google shipped them anyway, and so people began using them. Now Firefox has to live with the (unintended) consequence of their decision.
> Well, Chrome and Android are both Google projects; we could say that Chrome was late to FirefoxOS ;)
Sure, but marketshare! My point is, Mozilla is doubly disadvantaged by having to battle against a vertical entity (Google), AND also being very late to the game on that platform.
> I'd do a quick checking in FF or Chrome (whichever I had open) to spot glaring problems
I'm pretty sure this is what most people do, and that's the problem, because most of the danger is from stuff that's only subtly broken, that a quick look won't catch. The non-web world has automated tests to help with this. Maybe we need tests that can run inside the browser script engine to test our webapps.