It's a 7 part series: https://en.wikipedia.org/wiki/The_Secret_War_(TV_series)

So, you know, eat it in chunks

Out of curiosity, why would Apple's privacy statement on searches be any different than Google's?

I do not know specifically as I have not read Apple Maps policy but to choose Apple Maps over Google Maps says a lot. I use google maps personally. Apple maps is getting better, but it's not google maps. So one can assume, the choice to choose apple over google means, IMHO, is that with Apple Maps they do not track as much as google would/does. Apple stance on privacy, publicly, has been pretty good. Tracking is everywhere and DDG still is sticking to their privacy first method.

Lastly, I love that I can dump random searches from my weird brain into DDG without the feeling that I'm giving some random machine, data that at some point can tell someone what I may want or do or have searched. Everyone knows what you're doing on the toilet, everybody poops, but we still close the door for privacy.

I don't dig what they're doing, but I do kind of like the idea of a deconstructed getter/setter:

[ get, set ] = getterSetter(defaultValue)

as a wrapper around some stateful, immutable value (mutating the result of the get won't be tracked, that is)

That's pretty much what useState does. (or maybe you were already saying you liked that -- sorry, if that's what you meant) The only difference being that the "getter" has already been "executed" in a way: useState returns a value and a setter. Changing the value won't get tracked, and a call to the setter will overwrite the old value and re-render.

Yeah -- I'm saying it's dubious that there's magic here "doing the setState queue for you" -- notice the function call isn't bound and there's no passing of "this", so it's gotta' got some magic under the hood with some global context.

I do, however, like the concept for the react style of render -- being able to grab a getter/setter from that is awesome. They can remove the magic by simply doing:

const [getter, setter] = this.useState(...)

It's nothing more than React already knowing exactly _which_ component it's working on rendering. See my other comment here: https://news.ycombinator.com/item?id=18306957

I don't think that's the point -- the problem isn't that "oh there are other processes that [...]," it's that this wave of technology is misused, is bias, and care must be taken when any of the signals we create.

This is especially important as automation enters the equation.