The only real change since 1.0 was async. If you want to live without async that is completely up to you. It is an entirely optional part of the language.
If you want a language guided by the principle of simplicity Rust was never that and you have plenty of options elsewhere.
Except that many crates only provide an async interface. I actually use async for many things, but the whole colored functions thing is really annoying.
One trick to get out of this is to wrap any function with an asynchronous interface with pollster::block_on which turns the call back into exactly how it would have run if it had been synchronous (which leads to no color leaking).
Yes, easy enough but annoying. Going the other direction (async -> sync) is a bit more problematic though. Now you've got to wrap things in spawn_blocking(), which isn't nearly as benign.
Comments
The only real change since 1.0 was async. If you want to live without async that is completely up to you. It is an entirely optional part of the language.
If you want a language guided by the principle of simplicity Rust was never that and you have plenty of options elsewhere.
Except that many crates only provide an async interface. I actually use async for many things, but the whole colored functions thing is really annoying.
One trick to get out of this is to wrap any function with an asynchronous interface with pollster::block_on which turns the call back into exactly how it would have run if it had been synchronous (which leads to no color leaking).
Yes, easy enough but annoying. Going the other direction (async -> sync) is a bit more problematic though. Now you've got to wrap things in spawn_blocking(), which isn't nearly as benign.