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
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.
It's spread across all parts of the browser, but speaking as a Firefox graphics engineer, we use quite a lot of memory. Painting web pages can be slow, so we try to cache as much as possible. When elements scroll separately, or can be animated, we need to cache them in separate buffers. If we get the heuristics wrong (and it's hard to get it right for every web page out there) this can be explosive. It's not helped by the fact that graphics drivers can frequently bring down the whole process when they run out of memory. It's a hard problem, but webrender will help as it needs to cache less.
What's the red flag about a stack?