Perhaps FF developer edition was meant to test the waters for this approach? Do web people actually use that? I never got to the point of making it part of my p

Perhaps FF developer edition was meant to test the waters for this approach? Do web people actually use that? I never got to the point of making it part of my process, but I'm not doing enough web to really have a process. In any case, a dev browser can only be relevant if it's representative of end user browsers. The history of browser wars has shown that a superior dev experience can be a decisive factor in winning users, but it can never be more than a supporting role. These days a far more plausible dev level monetization angle would be Mozilla's unique position as the origin of Rust. Spin out a Rust subsidiary that sells service and perhaps also some premium tooling/SaaS in the open market while doing work on Rust/Servo/FF for a nominal fee that allows both sides to keep the lights on. But that (just like paid browser dev tools) would be B2B and apparently Mozilla Corp completely fails to see itself as a B2B actor outside of consumer eyeballs deals like the Google deal and the increasingly outbrainy start tab fillers. But failure to go that way is hardly surprising. Where would the business skillset come from when the entire organizion outside the tech teams has more in common with the great money furnaces of Wikimedia than with anything else? The only way I can see for that kind of transition to go well would be some form of merger/acquisition with someone already existing in those fields (consultancy and/or tooling). "you take the engineers, we'll be buying services". But the successful ones would be very reluctant to suddenly load themselves with the entirety of Rust. It would probably take someone owner-managed who brought a decent amount of idealism into the equation. Total number of candidates might amount to zero.