Async is really painful and a "not finished yet" thing. However, in practice, if you use Tokio you should be fine. And usually this decision will be made for y

Async is really painful and a "not finished yet" thing. However, in practice, if you use Tokio you should be fine. And usually this decision will be made for you with the framework you pick. My #1 tip is to decide on exactly what your use case is, then use cargo and look at the recent number of downloads and go with the most popular framework. Doing this for several tags (http, server, framework) is required for categories that are noisy or not tagged well. Example: Are you writing a web service API, a web server that has server-side templates, a client-side SPA app, or a server-less function? Usually you will see they are all aligning on the same stack tokio, serde, etc but this is definitely something to be aware of. It is critical that an application uses the same version of dependencies for cross cutting concerns.