For me Rust (after initial euphoria around 1.0 release) became the best option to do some heavy duty routines, like crunching through complicated large XML or c

For me Rust (after initial euphoria around 1.0 release) became the best option to do some heavy duty routines, like crunching through complicated large XML or calculating exotic things (that I can't bother to modify to run on a GPU). Basically synchronous CPU intense tasks. Thats kinda the sweet spot overall for me after the years. Completely gave up on using it for anything else. When I want concurrency/parallelism/distribution, just use the BEAM (iE: Elixir) which is literally made for that problem space. BEAM is not exactly good for computations, though (as are many other tech stacks)... so writing a native extension/library in Rust when there really is a demand is perfect - but any scheduling whatsoever stays in BEAM territory, including keeping an eye on the non-preemptive behavior of the Rust function and schedule calls to it properly. So for me, I don't need async (or even multicore) rust anymore to begin with, but the base functionality of the language (especially including serde!) knocks it out of the park for some problems like nothing else.