I use jj but not mega merges. But as I understand it you're not going to push the merge itself for review. It allows you to work locally on multiple branches at once. But when ready you push the individual branch, pre merge, for review.
There's a configurable setting for which changes are marked as immutable. The default works perfectly for my workflow (pull-only from upstream, rewrite and push freely to my fork). other workflows may presumably need to tweak it
Surely your criteria should be some combination of the two (plus other factors). C may have fewer footguns than C++, but it still has many, whilst also lacking many useful features
> Surely your criteria should be some combination of the two (plus other factors).
Sure, but the weighting would be different for different people.
> C may have fewer footguns than C++, but it still has many, whilst also lacking many useful features
We are not talking "2 fewer footguns", or "5 fewer footguns"; we are talking "dozens fewer footguns".
When I need a language with more features than C, I don't choose C++, because the choice is not "Use C for simplicity, and use C++ to trade simplicity off against features", it's usually "Use C for simplicity, and use Java/C#/Go/Rust for features".
I’m a Mozilla employee who works on Firefox, so I’ll try to answer this to the best of my knowledge but as a disclaimer I can’t guarantee I’m 100% correct
Paying for relay will give money to Mozilla Corporation, the same pot the google money goes into, which will predominantly pay for Firefox development but also other products. The corporation’s profits also fund the non-profit Foundation’s activities.
People often raise this argument regarding donating to the Foundation, as that money will be spent by the foundation, therefore not on Firefox. But a dollar raised by the foundation is a dollar less the corporation has to give the foundation, leaving it with more money to spend on Firefox and other things.
You can also donate directly to “MZLA” which makes thunderbird, and that money will be spent on thunderbird.
The problem many people have with donating to the Mozilla Foundation us them squandering enormous amounts of it. Mostly on things nobody asked for and executive pay.
Personally, I don’t feel like firing Firefox devs and starting controversial and expensive diversity campaigns while raising executive pay when Firefox is losing market share every year is being a great steward.
Did you consider using wgpu instead of writing a new dx11 renderer? It has metal, vulkan and dx12 backends so could have been used for a single renderer for macOS windows and Linux. (And webgpu in the future)
I am a Firefox developer, and you're spot on. Previously there were separate hg repos for central, beta, release. I think ESRs too. And autoland. Now they're all branches in the same repo, and central is renamed main.
Commits land in autoland and get backed out if they cause test failures. That's merged to main ~twice per day when CI is happy
I've mostly encountered these branches/repos when checking commits linked to Bugzilla tickets, and I don't recall seeing "autoland" show up too much in those cases.
What's the red flag about a stack?