My bet is that with adoption of useEffectEvent it will become much less common (for good). useEffect is already complex on its own, even without the need to build a mental tree of dependencies of callbacks

Yeah. I know how it works. But people just don’t write code like in your example because it is hard to track when function identity change

I doubt “most effects” but I feel it was already discussed many times on internet. Really glad we have useEffectEvent now! Really useful for perf optimizations. The only thing left is granular context subscriptions

Oh. Right. It is interesting that in real life I think I never seen an effect that was written to intentionally react to fn identity change. UseCallback with deps has a clean mental model but turned out not very practical

What was the reasoning to make use Callback to have a dependency array instead of making essentially like useEffectEvent?

Но кофе получается немного мутноватым и с осадочком. Воронка Clever - вот это идеал. Элементарно заваривать, вкусный кофе и не надо мыть, так как выкидываешь фильтр и все

@phoenix.tapbots.com will save us all

Зато храниться будет дольше

Круто получилось

Эласт Фандорин

Interestingly, it’s kinda liberating when you see an external reasons for your mood or thoughts