[moron4hire]

It's not my job to care about Firefox. My job is to deploy applications to my users. You make a better browser than Chrome, I can do that on Firefox. I mean, I already do support Firefox, but maybe I'd stop cursing your name when I have to do stuff like compromise on user experience because I can't offload large chunks of image processing onto a web worker because you still don't support 2D graphics contexts off the UI thread.

It's YOUR job to care about Firefox. And as far as I can tell, not enough people at Mozilla care enough about Firefox to make up for going from #2 browser in the world to numbers comparable to (checks notes) Samsung Internet. You complain about having to follow Google's lead. You aren't just following Google anymore. Y'all have to follow everyone.

And don't even talk to me about WebRTC. You folks have had 10 YEARS to get an act--any act--together around WebRTC. Firefox's WebRTC performance has been notoriously bad for that entire time. So, wait, let me get this straight. You complain about having to bend over backwards to appease Google's way of doing things. But now you're complaining about a case where Mozilla steadfastly refused to bend over backwards for Google for a decade? Over the format of the SDP lines. Because that's a hill worth dying on. Get out of here.

[wisniewskit]

Ah yes, the old "it's not my job" excuse. Then why are you here acting like an authority on this stuff, when you very clearly don't have the slightest clue? I mean, is your actual job to make excuses for Google and shift the blame to everyone else for Google's misbehaviour?

The folks who actually care and work on non-Chrome browsers have been telling us for a decade that Google is not being a good faith player, and is creating an obvious browser engine mono culture. And instead of listening to them, you ignore them to defend Google instead.

You're the one who should get out of here, and educate yourself on this stuff first before you talk big about it. Go find out just what a mess WebRTC has been thanks to Google and its ever-shapeshifting "plan B" (and not just from Google's point of view). It helped kill two major browser engines already, and it certainly wasn't because they didn't try to work with Google to figure it out, or spend a lot of time trying to reverse-engineer it as it changed, or even just trying to import enough of Chromium into their own browsers to ship "plan B" themselves after Google remained silent.

And while I'd love to help you with your pet bugs, including such basic web functionality as "offloading large chunks of image processing to a web worker", I'm here diagnosing live web sites to find that Chrome shipped `event.path` before it was standardized, or haven't fixed three year old bugs with `text-underline-offset`: things that are breaking such hyper-advanced and unimportant functionality on the web as clicking on links and underlining text properly.

So tell me again how I'm wrong and Google's bugs don't affect other browsers. And how it's my fault that Google seems to ignore interop bug reports until they become issues on live pages, and then conveniently say "well, the web relies on this now, so you change the standards and your own browsers to follow suit now"? I guess I need to be flawless myself before I have any right to complain about their bad behaviour?

Do go on. Tell me more about your theories about what I and other Mozilla folks do with our time, and how Google and its defenders aren't making it harder for us to do what we'd really rather be doing for our users.