see-dante

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?

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(...)

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)

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.