I worked on this for a couple years (have been much less active lately), surprised to see it on the front page of HN but happy to answer questions about it.
You're wrong I'm so many ways it's hard to know where to start, but one obvious one is that the teenager who was run over was not an anti-war protestor, he was protesting a potential change to exemption from military conscription for the ultra-Orthodox. Not a peacenik. Haredi conscription is a contentious issue but framing it as anti-war is disingenuous.
They're actually not doing that, they're doing the opposite of that, calling to bring back the secular shah to replace their current Islamic theocracy.
I worked at Google for ten years (as an IC). Here's my personal perspective.
Yes, of course, the individual employees know. But the decision making for these kinds of things is usually a full-time middle manager, who isn't deciding on behalf of Google as a whole, but on behalf of their organization within Google (could be 50 people, could be 2000). It's not just _not_ that manager's job to make the globally optimal decision for Google, it's actually likely often in direct conflict with their job, which is basically "set the priorities of your org such that they launch things that make your boss look good to his boss". Spending headcount on maintaining niche stuff is usually not that (and takes resources away from whatever is).
The hard part I always found without jj (and Fig before it, when I was at Google) was managing a DAG of small changes.
What's your git workflow for a change that depends on two other in flight changes? (More generally, of course, this can occur in an arbitrary part of one's change graph - which is usually not too deep, but at least in my experience, occasionally is.)
Having good tooling for this unlocked workflows I didn't know I was missing, and switching back to git when leaving Google felt like losing a limb.