3 ms·
Yes, you must deal with async It's not that big of a deal though Axum is popular but feels too low level to me, but some nice porcelain APIs might eventually
by imwithstoopid 4y ago
Yes, you must deal with async
It's not that big of a deal though
Axum is popular but feels too low level to me, but some nice porcelain APIs might eventually be put on top of it
- antonvs 4y agoWhat feels higher level to you than Axum? I picked Axum because it seemed higher level than the alternatives I looked at, including actix and warp.
- satvikpendem 4y agoThey're likely talking about Rocket which is higher level than Axum or Actix Web, but it's recommended not to use it as it's not as actively maintained, as well as some other issues. For a Rails-like experience, Nails [0] is one I've seen, although I don't know the status of it as no one seems to talk about it as much as Axum and Actix Web. [0] https://rust-on-nails.com/ https://rust-on-nails.com/
- linhns 4y agoI think axum is pretty decent tbh, considering it's part of Tokio and will get better support than most servers out there
- Animats 4y agoIt's possible to avoid async contamination in Rust. Game-type programs generally don't use it, because they're compute-bound. The use case for async is a huge number of mostly inactive network connections.
- earthling8118 4y agoWhat makes it feel low level to you? Axum has been my favorite way to do HTTP servers for some time. Especially where it is now, everything feels expressive, and I can do whatever I need to. If you're just doing basic stuff it makes it easy and if you're going beyond that it makes it possible. There are a few parts of the learning curve that come up but the official examples showcase it all beautifully and the community is very responsive if you ask for help.