4 ms·
Alternatively use async everywhere from the start and your headaches go away too. It's mixing blocking code with async code that causes issues.
by nicoburns 6y ago
Alternatively use async everywhere from the start and your headaches go away too. It's mixing blocking code with async code that causes issues.
- pvorb 6y agoJust do it if everyone in your team is comfortable with it. I'm just not as productive with async code.
- nicoburns 6y agoAh yeah, as someone whose first langauge is javascript where all IO and even things like timers are async, I forget that not everyone groks it. It's really not that complicated (at work we have junior devs with 6 months experience writing async code no problem), but I think there is a certain amount of unlearning that needs to be done if you're used to working with threaded code.
- lumost 6y agowon't this just bifurcate the rust ecosystem between async and non-async rust libraries?
- loeg 6y agoIt's already there.