HN user

jamienicol

371 karma
Posts0
Comments183
View on HN
No posts found.

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.

What's the red flag about a stack?

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

Helium Browser 10 months ago

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

Searching for World cup matches in google only shows the goal score, I guess it's a google search issue, but in chrome I get detailed scorecards

Go to settings -> add ons and install "Google search fixer"

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

I'm not sure what should be done about it, but again don't see the relevance of that question. Your argument was that there's value to be had out of such a debate, which there isn't. And that a debate cannot be misinformation, which is again clearly false. Packaging misinformation up as a debate doesn't stop it being misinformation.

To be fair though, the freeze was probably caused by a xul extension.

I switched from Gmail to fastmail last week, after planning to do so "one day" for a few years. Using a mixture of the web client and Thunderbird, just like I did when using Gmail. No regrets so far, I recommend taking to leap!

Firefox 94 5 years ago

Or maybe, just maybe, people have a different opinion to yourself about how Mozilla can succeed.

It could be because it matches the order of glsl's `mix()`. Not sure why glsl chose that order, though perhaps you might find it less unintuitive for an interpolation than a select. (Mix acts as a select rather than interpolation when the third argument is a boolean)

Actually the guardian headline is perfectly accurate. It completely is accurate to say the algorithm has a bias, even if that bias isn't "if (right-wing) then amplify()"

If you search for the word “bias” in Twitter’s post you’ll not find support for The Guardian’s editorialization

But if you search for "favour" you'll find "[our findings revealed that] algorithmic amplification favours right-leaning news source". In the abstract. Which means the exact same thing.

Here’s an important excerpt, which notes that more analysis is needed to understand whether the amplification is unnatural relative to user interactions

The guardian article includes your quote so I don't think you can accuse it of omitting important context.

Twitter’s internal research is saying that certain tweets are organically more popular and engaging and more likely to be shown

I'm not sure where you're reading this from. It is pretty explicit that further research is required in to the cause of the discrepancy.