And by that definition, why would anybody not call themselves a "lefty"

2. bobaekang.com/blog/what-we...

Fantastic!👏

Bookmarked for future reference

I remember there being a lot of talk about this. Simple memoize utils on npm had pretty high usage in the react community. You basically just created a memoized function in the constructor (cWM) and called in render.

You have always been able to just calculate in render, but useMemo didn't exist, so for expensive calculation some of us used a memoized function. But yeah, most people probably didn't do that.

Why is there a need for "pending"? I mean, if the status is undefined it needs to be unwrapped/awaited anyway?

I'd rather be proactive than reactive in this area

Agree to disagree?

The rewrite of the "terms of use" "promise" didn't look very good. I have read their explanation but I still don't understand how that could happen like that. Also, it's very unfortunate that they (you?) are dependent on the google deal.

Simultaneously I'm not sure if Mozilla is the best company for this task. They have done some some things that I definitely don't agree with. But as of now they are what we've got. Tho them hiring @jakearchibald.com made me a bit calmer.

On top of this they are often a sound voice in the committees. They have a voice because their browser has users.

This said, I also like FF as a browser. The team is amazing and I very much respect their work.

In the end this comes down to ideologies. I support ff because I remember the past. Ff has been _very_ important in getting to where we are and I'm not sure what would happen if they didn't exist anymore. I have seen too many malicious pushes from big tech (latest being the adblock stuff).

So the solution in that case is more browser engines?