2 ms·
> All that async continuation passing makes your code a twisty maze On the contrary, it gives your code clarity, consistency and predictability. > some master
by zzzcpan 11y ago
> All that async continuation passing makes your code a twisty maze
On the contrary, it gives your code clarity, consistency and predictability.
> some master continuation that will delete them all in the final callback
Even nginx in plain C is not doing that, but simply creates destructors on allocation to avoid tracking stuff manually.
Just don't jump into the first thing you read somewhere, remember one simple rule: if it feels harder than threads - you are doing it wrong.
- SamReidHughes 11y ago> On the contrary, it gives your code clarity, consistency and predictability. Well, when a product I worked on gradually migrated from event loops with callbacks to threads, clarity, consistency, and predictability made big improvements. Some callback usage would have been better with C++11 or C++14, but it's still way worse than what you can do simply by having variables go in and out of scope on a stack.