I, too, have been saying this on occasion. In my observation, Mozilla has been in an increasingly suboptimal position with Firefox, for a while now, as Google and Microsoft have largely settled on splitting the market in between themselves where the core of Chrome is developed by the former and Microsoft spends their effort on what they are [better] at -- integration with Windows in the form of UX-level features and whatever else that they do with it to build Edge. Firefox is increasingly seen as a "fair" nuisance that is slower, and by comparison can afford less effort development-wise. Look at some of the practically critical issues in their Bugzilla database -- there are features there that have been waiting almost a decade for implementation, and the discussions point to a combination of code complexity that requires acute insight into the browser that is your typical bell curve distributed over developers familiar with it -- the number of developers who are able to actually deliver on those features, can probably be counted on two hands. And that is in part because most of these people are getting paid to do other things. In the very least Mozilla directs their effort in a manner that speaks for itself -- why are some of these features, like
https://bugzilla.mozilla.org/show_bug.cgi?id=1360870 that would be considered critical in today's Web development environment, not implemented after nearly a decade? -- If Mozilla _is_ paying the developers?
This is why I too think we ought to migrate to Patreon-like direct sponsoring of individual (or vetted group) effort to generate some development steam for Firefox. It might make Mozilla deny these developers write-access to Firefox repositories for all I know, but a fork cannot be prevented.
I've been using Firefox since its "Phoenix" days (good memories!), but it's lagging behind the competition more and more, and while I'd be first to admit we don't need half the features Google is busy putting into Chrome which then "magically" appear in Edge (what a devious alliance, that), some of them are sound design but are absent in Firefox, to the detriment of developers. In short: Firefox is losing more ground faster than ever before, at some point the boundary conditions will cause it to no longer be a viable alternative for the average user, I am afraid. Which will cause a "cascading failure" where no developer will test for it, and you know what happens then (because we've been there before).