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.
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
Because people are interested in how technology is built, and if they’re interested in rust they might be interested in seeing how it’s used in other projects
Perhaps it's because you didn't start the exchange with enquiry, but instead claimed that what happens in your country is "exactly what every country does"
It's certainly not normal in my country for schools to display the country's motto or flag, nor do children pledge allegiance to anything. We did sing some hymns though.
Some examples of things I've used telemetry for at Mozilla:
* Noticed performance regressions not caught by our testing, and therefore been able to fix the regression.
* Noticed an unexpected number of users with hardware acceleration disabled, and therefore been able to find and fix the bug that was causing them to have acceleration switched off
* Figure out which device in a category is most commonly used by our users, so that I can dogfood my work on a representative device
Those are just a few examples off of the top of my head. It's not about removing features because telemetry says nobody uses them. People Mozilla use telemetry to answer all sorts of important questions. We also have to jump through hoops to add any new data collection, justifying why it's needed and ensuring the data is not personal. As is right, because we take user privacy very seriously