Thanks for sharing -- for me: * actix-web: Pros: good docs, well supported, good eco system, Actor model fits very well with how I build systems (Actor ~= C

Thanks for sharing -- for me: * actix-web: Pros: good docs, well supported, good eco system, Actor model fits very well with how I build systems (Actor ~= Component) Cons: some ceremony around setup of the app object * tower-web Pros: good ergonomics, much easier to wrangle app state Cons: all-in-one macro is a bit hard to reason about, hard to split up bits of API (I might have just not known enough about how to break up the impl_web! macro) * warp Pros: express-y (req, resp) => result interface, surprisingly feature complete (http2, sse, websockets) due to building off of simple interfaces/extension points, functional APIs that are easy to compose Cons: very new, kind of experimental, docs are a little lacking but examples help