As a developer, I have to agree. Though I really don't want Google to dominate[*], and for there to be a good alternative to Chrome (and I keep using Firefox myself on principle), it's very hard to avoid recommending against using Firefox when they just don't try to keep pace with simple features. Two examples:
* Firefox still doesn't support "input type=date". There's a long thread, arguing about which UI widget would make the best native experience, but for a developer, all I care about is that there should be *some* widget, however imperfect it might be.
* Firefox on Android doesn't support "mobile-web-app-capable". That's essential for us, because it allows mobile sites to be launched full-screen from a desktop icon, without showing the URL-bar and back/forward controls. For our warehousing application (running on an android hand-held terminal with barcode-scanner), this is critical to prevent user-confusion.
On the other hand, at least Firefox isn't the terribly obsolete mobile-safari (still no WebRTC!), which will only get fixed if the a developers' lawsuit succeeds in forcing Apple to open up.
[*] Google have far too much power, and abuse of Chrome could be much more dangerous to the open internet than IE could have been back at the time.